Connect Cline / Continue

Prerequisites

VS Code with Cline or Continue installed
A Wicket member key — see the Quickstart if you don’t have one yet

Using VS Code’s native MCP support with Copilot agent mode instead? See Connect VS Code.

Configuration

Cline
Continue

Cline stores MCP config at:

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

Add under mcpServers:

{
  "mcpServers": {
    "wicket": {
      "url": "https://mcp.wicket.sh/mcp",
      "headers": {
        "Authorization": "Bearer <your-member-key>"
      }
    }
  }
}

Or use the Cline sidebar → MCP Servers → Edit MCP Settings to open the file directly.

Edit ~/.continue/config.json and add under mcpServers:

{
  "mcpServers": [
    {
      "name": "wicket",
      "transport": {
        "type": "http",
        "url": "https://mcp.wicket.sh/mcp",
        "requestOptions": {
          "headers": {
            "Authorization": "Bearer <your-member-key>"
          }
        }
      }
    }
  ]
}

Verify

Open a chat in your extension and ask it to use a tool from your connected connector. Confirm the call appears in the Wicket Audit tab.

Troubleshooting

Symptom	Likely cause
No tools available	Settings file path wrong or extension not reloaded
`401 Unauthorized`	Wrong or expired member key — regenerate in Wicket
`403 Forbidden`	Agent disabled or member not `approved`
Tool call blocked	Policy deny — check the Audit tab