Connect Zed

Prerequisites

• Zed with the Agent Panel enabled
• Node.js installed (npx is used to run the bridge)
• A Wicket member key — see the Quickstart if you don’t have one yet

Configuration

Zed launches MCP servers as local processes (stdio), so use mcp-remote as the bridge to Wicket’s HTTP endpoint.

Open Zed settings (cmd-, / ctrl-, → Open Settings (JSON)) and add a context_servers entry:

{
  "context_servers": {
    "wicket": {
      "source": "custom",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.wicket.sh/mcp",
        "--header",
        "Authorization: Bearer ${WICKET_KEY}"
      ],
      "env": {
        "WICKET_KEY": "<your-member-key>"
      }
    }
  }
}

mcp-remote expands ${WICKET_KEY} from the server’s environment, so the key lives in the env block rather than inline in the header string.

Tip

You can also add it from the UI: Agent Panel → Settings → Add Custom Server, with npx as the command and the args above.

Verify

1. Open the Agent Panel settings — wicket should show a running indicator.
2. In a new agent thread, ask: List my GitHub repositories.
3. Confirm the call in the Wicket Audit tab.

Troubleshooting

Symptom	Likely cause
Server shows as failed	npx not on Zed’s PATH — install Node, or use an absolute path to mcp-remote
401 Unauthorized in the server log	Wrong or rotated member key — update WICKET_KEY
403 Forbidden	Agent disabled or member not approved
Tool call blocked	Policy deny — check the Audit tab for the matched rule