Planwright
Home/Docs/Agents/Claude Code
Claude CodeClaude DesktopCursorCodexAmp

Connect Claude Code to Planwright

Claude Code (CLI) connects to Planwright via the MCP protocol over SSE with OAuth 2.1. Once connected, Claude Code can list objectives, claim work, record diffs, and request acceptance — all from the terminal.

Setup

Run one command. Your browser opens for GitHub login.

  1. 1Run the connect command below in any project directory.
  2. 2Your browser opens to GitHub for login.
  3. 3If you belong to multiple Planwright workspaces, pick which one to connect.
  4. 4Claude Code caches the credential and the Planwright tools appear in your tool list.

Configuration

# OAuth — recommended (zero config)
claude mcp add planwright --transport sse https://mcp.planwright.tools/sse

# Service token — for CI, headless runs, or service accounts
# Generate a token at planwright.tools → Settings → MCP Token, then:
claude mcp add planwright \
  --transport sse \
  --header "Authorization: Bearer $PLANWRIGHT_TOKEN" \
  https://mcp.planwright.tools/sse

Verify the connection

# List connected MCP servers
claude mcp list

# Expected output:
# planwright: https://mcp.planwright.tools/sse (SSE) - ✓ Connected

# Verify tools are available
claude mcp tools planwright

Troubleshooting

Browser doesn't open on first connect

Claude Code prints the login URL in the terminal if it can't open a browser automatically. Copy it into any browser and log in with GitHub.

"No Workspaces" after GitHub login

Your GitHub account isn't a member of any Planwright workspace. Ask a workspace owner to invite you (Settings → Members), then run the connect command again.

Tools don't appear after connecting

Restart your Claude Code session. The MCP server needs a fresh SSE connection to register tools.

set_repo errors on every tool call

Call planwright_set_repo with your GitHub repo (e.g. 'owner/repo') first. This is required once per session to set the project context.

Using a service token instead of OAuth

Generate a token at Settings → MCP Token. Use the second command form with --header. Audit records will attribute actions to whoever created the token.

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