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. Use the Streamable HTTP transport with the /mcp endpoint. OAuth opens a browser for GitHub login on first use and your GitHub identity shows up in audit records. Service tokens are available for CI and headless agents.
Setup
Add the Planwright server to your Amp MCP configuration.
- 1Add the Planwright MCP server using the config below.
- 2Restart Amp or reload tools.
- 3On first tool call, your browser opens for GitHub login.
Configuration
// Streamable HTTP + OAuth — recommended
{
"mcpServers": {
"planwright": {
"type": "http",
"url": "https://mcp.planwright.tools/mcp"
}
}
}
// Service token — for CI or headless runs
// Generate a token at planwright.tools → Settings → MCP Token
{
"mcpServers": {
"planwright": {
"type": "http",
"url": "https://mcp.planwright.tools/mcp",
"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
Which transport should I use?
Use Streamable HTTP (type: 'http', /mcp endpoint) — it's the only supported path. SSE (/sse) is deprecated and will be removed on 2026-10-01.
Amp can't connect to the server
Verify the URL has no trailing slash and uses https: https://mcp.planwright.tools/mcp. 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.