Connect Claude Cowork

Claude Cowork is Anthropic’s agentic workspace in the Claude desktop app — Claude works on multi-step tasks with your files and tools. Pointing Cowork’s tool access through Wicket gives those sessions the same policy guardrails and audit trail as your other MCP clients, which matters more in Cowork than anywhere else: Cowork sessions act autonomously for many steps at a time.

Prerequisites

• Claude desktop app with Cowork available on your plan
• A Wicket member key — see the Quickstart if you don’t have one yet

Configuration

Cowork uses the Claude desktop app’s MCP servers. Add Wicket to the desktop config file — the same entry that powers Claude Desktop chats:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Restart the Claude app. Wicket’s tools — github__*, slack__*, and the rest of your connected services — are now available to Cowork sessions alongside Claude’s built-in file tools.

Note

Cowork is evolving quickly and surfaces connectors slightly differently across builds and plans. If your build manages connectors only through the claude.ai Connectors directory (browser-based custom connectors), note that those require the remote server to offer an OAuth sign-in flow — Wicket authenticates MCP clients with Bearer member keys today, so use the desktop config path above. Contact support if your organisation needs the managed-connector path.

Recommended policies for Cowork

Autonomous, long-running sessions deserve tighter rails than interactive chat:

• Forbid the destructive tier on every connected service — recipes
• Add a session circuit breaker — forbid everything after 3 denied attempts in one session, so a runaway plan stops instead of probing: Tool sessions
• Scope to resources — confine Cowork to the repos/channels it’s meant to touch: resource conditions
• Set deny messages so Claude sees why a step was blocked and can re-plan around it instead of retrying

Verify

Start a Cowork session and ask Claude to list my GitHub repositories as part of a task. The call shows in the Wicket Audit tab; the session itself appears under tool sessions with its running tool counts.

Troubleshooting

Symptom	Likely cause
Wicket tools missing in Cowork	Config file not saved, app not restarted, or your build manages connectors via claude.ai only (see note above)
401 Unauthorized	Wrong or rotated member key — regenerate in Wicket
403 Forbidden	Agent disabled or member not approved
Session keeps getting blocked	Circuit-breaker policy tripped — an owner resets the session from the dashboard