Connect Claude Desktop to Planwright

Claude Desktop has a native UI for connecting to remote MCP servers — no JSON config to edit. Add Planwright as a custom connector, click through GitHub login, and the tools appear in your tool picker. Editing claude_desktop_config.json is now a fallback for legacy setups or headless debugging.

Setup

Custom Connectors are available on Claude Pro, Max, Team, and Enterprise plans. Free tier can't add remote MCP servers in the UI — use the JSON fallback below or upgrade.

1Open Claude Desktop and click the gear / Settings icon.
2Pro / Max: Settings → Customize → Connectors → click the + button. Team / Enterprise: an admin must first add it under Organization settings → Connectors, then members Connect from Customize → Connectors.
3Choose 'Add custom connector' (Pro/Max) or 'Custom → Web' (Team/Enterprise).
4Paste the URL: https://mcp.planwright.tools/sse
5Click Add. Your browser opens for GitHub login on first use, then a workspace picker if you belong to more than one.
6Planwright tools appear in the conversation tool picker (the hammer / tools icon).

Configuration

# Claude Desktop URL to paste in "Add custom connector":

https://mcp.planwright.tools/sse

# That's it — no JSON, no headers, no token. OAuth handles the rest.
# Need a service token for CI / headless / shared agents instead?
# Generate one at planwright.tools → Settings → MCP Token,
# then paste the token in "Advanced settings" when adding the connector.

# ─── Fallback: claude_desktop_config.json (legacy / headless only) ───
# Only use this on Free tier or when the UI isn't available.
# Mac:     ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json

# OAuth via mcp-remote bridge:
{
  "mcpServers": {
    "planwright": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.planwright.tools/sse"
      ]
    }
  }
}

# Service token via mcp-remote bridge:
{
  "mcpServers": {
    "planwright": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.planwright.tools/sse",
        "--header",
        "Authorization: Bearer YOUR_TOKEN"
      ]
    }
  }
}

Verify the connection

Once added:
1. Open a new conversation in Claude Desktop.
2. Click the hammer / tools icon.
3. You should see Planwright tools listed:
   - planwright_set_repo
   - planwright_list_workspaces
   - planwright_list_objectives
   - planwright_create_objective
   - planwright_list_phases
   - ... and more

Ask Claude: "List my scheduled objectives on Planwright"
— it will call set_repo and list_objectives automatically.

Troubleshooting

I'm on Claude Free and don't see 'Connectors'

Custom Connectors are gated to Pro, Max, Team, and Enterprise. Either upgrade or use the JSON fallback config in claude_desktop_config.json (shown above). The mcp-remote bridge runs on stdio and doesn't depend on the Connectors feature.

Team / Enterprise: 'Add custom connector' option missing in Customize

Org admins must add the connector under Organization settings → Connectors first. After that, individual members see it under Customize → Connectors and click Connect to authorize their own GitHub account.

Browser doesn't open for OAuth

Claude Desktop falls back to printing the URL — copy it from the connector dialog and paste into a browser. Once you finish GitHub login, return to Claude Desktop and the connector flips to Connected.

Tools don't show up after adding the connector

Open a new conversation (existing conversations may not pick up newly added tools until restarted). Verify in Settings → Connectors that Planwright shows 'Connected' rather than 'Needs auth.'

Editing claude_desktop_config.json: tools don't load after restart

Check the JSON for syntax errors — no trailing commas, no comments. Validate at jsonlint.com. Confirm Node is installed and on PATH; mcp-remote runs via npx.

MCP server not available

URL must be exactly https://mcp.planwright.tools/sse — no trailing slash, https only. Check that your firewall or VPN isn't blocking outbound HTTPS.

← Quick install (all agents)Sign in to Planwright →