Connect Amp to Planwright

Amp (by Sourcegraph) supports MCP for tool integration. Connect Amp to Planwright so it can read objectives, claim work, and report progress. The recommended path is OAuth — your GitHub identity is what shows up in audit records. Service tokens remain available for CI and headless agents.

Setup

Add the Planwright server to your Amp MCP configuration.

1Add the Planwright MCP server (OAuth config below) to your Amp configuration.
2Restart Amp or reload tools.
3On first tool call, your browser opens for GitHub login.

Configuration

// OAuth — recommended (zero config)
{
  "mcpServers": {
    "planwright": {
      "type": "sse",
      "url": "https://mcp.planwright.tools/sse"
    }
  }
}

// Service token — for CI or headless runs
// Generate a token at planwright.tools → Settings → MCP Token
{
  "mcpServers": {
    "planwright": {
      "type": "sse",
      "url": "https://mcp.planwright.tools/sse",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Verify the connection

After configuring, ask Amp:
"What are my scheduled objectives on Planwright?"

Amp should connect to the MCP server and return results
from planwright_list_objectives.

Troubleshooting

Amp can't connect to the server

Verify the URL is https://mcp.planwright.tools/sse (no trailing slash). For the token form, the Authorization header must include 'Bearer ' (with a space) before the token.

OAuth flow doesn't open a browser

If your Amp build doesn't yet support OAuth discovery, switch to the service-token config and generate a token at Settings → MCP Token.

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