Connect a client

Every MCP client talks to Wicket through one endpoint:

https://mcp.wicket.sh/mcp

Authenticate with your member key as a Bearer token — the key alone identifies you and your agent; there is nothing else to configure. Wicket aggregates the tools of every connector your agent has enabled and exposes them with a service prefix (github__get_file_contents, slack__slack_send_message, linear__save_issue). The guides below show the exact config for each client.

Claude Desktop

JSON config file on macOS and Windows. → Connect Claude Desktop

Claude Code

CLI command or ~/.claude.json, with project-scoped option. → Connect Claude Code

Cursor

Global or project-scoped mcp.json. → Connect Cursor

VS Code & Copilot agent mode

Native mcp.json with secret-storage inputs. → Connect VS Code

GitHub Copilot

Agent mode in any editor, plus the coding agent on github.com. → Connect Copilot

Zed

Agent Panel via the mcp-remote bridge. → Connect Zed

Claude Cowork

Govern autonomous Cowork sessions. → Connect Cowork

Cline / Continue

Extension-specific config files. → Connect Cline / Continue

Codex (OpenAI CLI)

Uses mcp-remote as a stdio adapter. → Connect Codex

What you need

Before configuring any client, you need a member key — generated from the agent’s Members tab in the Wicket dashboard. It is shown once; copy it before closing. If you don’t have an agent yet, start with the Quickstart.