Plugins & MCP
resolve ai ships plugins for claude code, codex and cursor that connect your coding agent to resolve ai over mcp the plugins are currently in open beta open and steer investigations, ask follow up questions, pull production context, and turn root cause findings into pull requests directly from your coding agent the plugin is available at resolve ai oss/resolve ai plugins https //github com/resolve ai oss/resolve ai plugins what you can do common workflows once the plugin is installed pull production context before a risky change before editing application code, infrastructure, or migrations, ask the agent to surface the area's traffic, telemetry coverage, baseline error rate, recent deploys, and open alerts join an incident or resolve investigation connect to an existing incident or investigation in resolve from your coding agent pull findings and recommendations, steer it with context you have locally, and start multiple parallel threads of investigation inside the same shared context drive reliability sprints and oncall work from your editor have resolve surface recent chats and investigations, then step through fixes from your coding agent at your own pace wire resolve into your own skills have your own skills kick off resolve investigations as part of your developer productivity stack install resolve ai plugin claude code /plugin marketplace add resolve ai oss/resolve ai plugins /plugin install resolve ai\@resolve ai plugins restart claude code /mcp should show resolve connected codex codex plugin marketplace add resolve ai oss/resolve ai plugins codex plugin add resolve ai\@resolve ai plugins codex mcp login resolve restart codex /mcp should show resolve connected cursor in the cursor dashboard, open plugins and add a team marketplace, importing this repository https //github com/resolve ai oss/resolve ai plugins assign the marketplace to the right distribution groups, then install resolve ai from cursor's marketplace panel restart cursor the resolve mcp server should appear in settings > mcp authentication the mcp transport uses oauth on first connect, the host (claude code or codex) discovers resolve oauth and prompts you to sign in no api key is needed for normal plugin usage for mcp only clients that don't support the plugin, point at the mcp endpoint directly https //app0 resolve ai/mcp/v2 authenticate with a personal api token created at user menu > personal api tokens , passed as authorization bearer \<token> for shared service integrations, use an organization token from admin > api tokens instead skills the plugin installs the following skills your coding agent invokes them by intent or as slash commands skill use it for alerts list and filter firing alerts by team, time range, label, severity, or auto investigation status ask ask resolve a question in a new chat or as a follow up to an existing chat or investigation apply fix translate resolve's root cause findings into local code changes and a pr chats list recent resolve chats and see which ones are still running demo run a guided tour of resolve using live data from the connected org feedback capture a verdict on an investigation, chat answer, or the product when work wraps up help resolve explain resolve and route the user to the right workflow investigate open an existing resolve investigation or start a new rca from a problem description investigations list and filter recent investigations by team, run type, use case, and time range overview get a compact snapshot of investigations, alerts, and chats prod context pull production context before implementing a risky code, infra, config, or migration change steer send a finding, hypothesis, or directive into an active resolve investigation mcp tools skills are built on top of the following mcp tools, also available directly to any mcp client connected at /mcp/v2 tool description ask send a question or request to resolve in a new or existing chat or investigation start investigation kick off a deep root cause investigation from a problem description steer investigation send a finding, hypothesis, or directive into an active investigation get investigation get the full state of an investigation (report, theories, alerts, mitigations) list investigations list investigations by team, run type, use case, label, and time range get chat get the messages and current state of a chat list chats list recent chats list alerts list and filter alerts read file read a file path returned by resolve (cited evidence, report sections) upload attachment upload an attachment for use in a chat or investigation submit feedback submit feedback on an investigation, chat answer, or the product live progress ask , start investigation , and steer investigation may return a stream command a self contained curl for following live progress the host agent runs it as a background process and reads stdout until the operation completes the command carries a short lived scoped watch token, so no api key is needed where to go next admin plugin docid\ fcbokmaj0ofzk39ya5x1a companion plugin for administrators who manage resolve integrations migrating from the mcp beta docid\ selklh n5l1smfnrbtiwa switch from the old /mcp endpoint and manual setup to the plugin