Migrating from the MCP Beta

resolve's mcp server moved from /mcp to /mcp/v2 , with oauth and the plugin install flow described in plugins & mcp docid\ ua3ug9n74xxua2pjq1y5v the old endpoint and its tools are documented below for reference migration steps if you previously configured resolve mcp manually in your ai coding agent or assistant remove the old resolve mcp server entry from your host config remove any old resolve api key from your shell profile or host config install resolve ai from the plugin marketplace following install docid\ ua3ug9n74xxua2pjq1y5v sign in with oauth when prompted restart your host /mcp should show resolve connected mcp only setup for clients that don't support the plugin, or if you'd rather configure mcp manually, point your client at https //app0 resolve ai/mcp/v2 you'll get the same resolve mcp tools, but not the bundled plugin skills authenticate with a resolve api key (see authentication docid\ ua3ug9n74xxua2pjq1y5v for how to generate one) sent as a bearer token most hosts take a static header "resolve" { "type" "http", "url" "https //app0 resolve ai/mcp/v2", "headers" { "authorization" "bearer ${resolve api key}" } } codex codex uses toml https //toml io/en/ and a bearer token env var field instead of a header \[mcp servers resolve] url = "https //app0 resolve ai/mcp/v2" bearer token env var = "resolve api key" cursor cursor's mcp json references env vars as ${env\ name} , not the bare ${name} "resolve" { "type" "http", "url" "https //app0 resolve ai/mcp/v2", "headers" { "authorization" "bearer ${env\ resolve api key}" } } legacy reference this is the previous mcp server documentation the endpoint and tool names below have been replaced by the plugin's /mcp/v2 endpoint and the tools listed in mcp tools docid\ ua3ug9n74xxua2pjq1y5v endpoint https //app0 resolve ai/mcp transport streamable http https //modelcontextprotocol io/specification/2025 03 26/basic/transports#streamable http (stateless, no session management required) setup (claude code) add to your mcp json { "mcpservers" { "resolve" { "type" "http", "url" "https //app0 resolve ai/mcp", "headers" { "authorization" "bearer ${resolve api key}" } } } } set resolve api key as an environment variable with your api token, then restart claude code tools resolve start chat start a new conversation with resolve parameter type required description message string yes message to send to resolve returns the full response text and a canvas url resolve start investigation kick off a deep (rca style) investigation and return the initial investigation response along with the canvas url equivalent to toggling deep investigation in the resolve chat ui the investigation continues in the background on the canvas after the tool returns parameter type required description message string yes investigation prompt to send to resolve canvasid string no existing canvas id to continue from before starting the investigation returns the transition message, the canvas url, and the canvas id use resolve get investigation with the canvas id to poll progress and retrieve the full report once the investigation completes reply send a follow up message to an existing conversation use the canvasid from a previous resolve start chat result parameter type required description canvasid string yes canvas id from a previous resolve start chat result message string yes follow up message resolve list investigations find past investigations by time range and alert labels parameter type required description starttime string yes iso datetime for the start of the search window endtime string yes iso datetime for the end of the search window labels object no filter by alert labels all specified key value pairs must match resolve get investigation get full details of a specific investigation including status, rca reports, and theories parameter type required description canvasid string yes canvas id from resolve list investigations notes resolve start chat blocked until resolve finished responding simple questions returned in under a minute to kick off a deep investigation, resolve start investigation was preferred it returned the canvas url quickly and the investigation continued in the background including /rca in a resolve start chat message also worked (the backend detected the trigger word) each tool call was independent no session state was maintained between requests