Connect Claude Code

Prerequisites

• Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
• A Wicket member key — see the Quickstart if you don’t have one yet

Configuration

CLI (recommended)

Run once to register the server:

claude mcp add --transport http \
  --header "Authorization: Bearer <your-member-key>" \
  wicket \
  https://mcp.wicket.sh/mcp

This writes to ~/.claude.json under mcpServers.

Manual config

Edit ~/.claude.json directly:

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

Project-scoped

To scope the server to one repo, add a .mcp.json file in the project root instead of the global file. Same JSON structure as above.

Tip

Run claude mcp list to confirm the server registered, and claude mcp get wicket to inspect its config.

Verify

Start Claude Code in any directory and ask:

> List my GitHub repositories.

The tool call routes through Wicket. Check the Audit tab in the Wicket dashboard to confirm the decision.

Troubleshooting

Symptom	Likely cause
Server not listed in /mcp	Registration failed — re-run claude mcp add
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 for matched rule