How-To Guides

Connect a coding agent

Planwright is MCP-native. Agents connect via the Planwright MCP server and interact through structured tool calls — listing objectives, claiming work, posting plans, recording diffs, and requesting acceptance. Here's how to get connected.

1. 1

   Sign into Planwright

   Go to planwright.tools and sign in with GitHub. Your workspace is created automatically from your GitHub organization on first login.

2. 2

   Choose your authentication method

   Most agents support OAuth — your browser opens for GitHub login and the credential is cached automatically. For CI pipelines, headless runs, or shared service accounts, use a service token instead.

   OAuth (recommended)

   Browser login via GitHub. No token to manage. Audit records show your GitHub identity.

   Service token

   Generate at Settings → MCP Token. For CI and headless agents.

3. 3

   Follow the setup guide for your agent

   Each agent has its own configuration format. Pick yours below for the exact commands and config snippets.

   Claude CodeOne command — browser login via GitHub OAuth.

   →

   Claude DesktopAdd as a custom connector in Settings.

   →

   CursorAdd a .cursor/mcp.json file to your project.

   →

   CodexOne command or a JSON config file.

   →

   AmpAdd to your Amp MCP configuration.

   →
4. 4

   Verify the connection

   Once connected, ask your agent to call planwright_list_workspaces to confirm the MCP tools are available and the auth flow completed. Then call planwright_set_repo with your GitHub repo to set the project context for the session.

   planwright_set_repo is required once per agent session. Without it, every other Planwright tool call will fail.