Skip to content

Cline Integration Guide ​

Configure GitLab MCP for Cline (VS Code extension).

Auto-Setup ​

bash
npx @structured-world/gitlab-mcp install --cline

Detection ​

MethodDetails
TypeExtension storage directory
Extension IDsaoudrizwan.claude-dev
Auto-detectedYes (when extension storage exists)

Config File Location ​

OSPath
macOS~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Windows%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
Linux~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Configuration ​

Add to your cline_mcp_settings.json:

json
{
  "mcpServers": {
    "gitlab": {
      "command": "npx",
      "args": ["-y", "@structured-world/gitlab-mcp"],
      "env": {
        "GITLAB_TOKEN": "glpat-xxxxxxxxxxxxxxxxxxxx",
        "GITLAB_API_URL": "https://gitlab.com"
      }
    }
  }
}

Remote Server ​

Connect to a running GitLab MCP HTTP server:

json
{
  "mcpServers": {
    "gitlab": {
      "type": "streamableHttp",
      "url": "http://localhost:3333/mcp"
    }
  }
}

Cline's transport identifier is streamableHttp. You can also add the endpoint through MCP Servers > Remote Servers, choosing Streamable HTTP. Use Configure MCP Servers to locate the IDE extension's active configuration file; the CLI uses a separate configuration. See Cline's MCP guide.

Verification ​

  1. Open VS Code with the Cline extension installed
  2. Open the Cline panel
  3. Check MCP server status in Cline settings
  4. GitLab tools should appear in the available tools list

Troubleshooting ​

  • Config path not found: Install the Cline extension first, then the settings directory will be created
  • Server not connecting: Reload VS Code window after config changes
  • Extension ID changed: Verify the extension is saoudrizwan.claude-dev in your VS Code extensions

See Also ​

Released under the Apache 2.0 License.