> ## Documentation Index > Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt > Use this file to discover all available pages before exploring further. # AI Assistant Plugins ResolveAI ships plugins for Claude Code, Codex and Cursor that connect your coding agent to ResolveAI over MCP. 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 ResolveAI Plugin Install from the host's own marketplace where there is one, or from the ResolveAI plugin repo. Either way, the plugin authenticates over OAuth — see [Authentication](#authentication). ### Claude Code **Option 1: Install from the Claude Code community marketplace** ```text theme={null} /plugin marketplace add anthropics/claude-plugins-community ``` ```text theme={null} /plugin install resolve-ai@claude-community ``` Restart Claude Code, then run `/mcp`, review the connection status of the `resolve-ai` plugin, and authenticate to your ResolveAI organization when prompted. **Option 2: Install from the ResolveAI plugin repo** ```text theme={null} /plugin marketplace add resolve-ai-oss/resolve-ai-plugins ``` ```text theme={null} /plugin install resolve-ai@resolve-ai-plugins ``` Restart Claude Code, then run `/mcp`, review the connection status of the `resolve-ai` plugin, and authenticate to your ResolveAI organization when prompted. ### Codex ```sh theme={null} 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 **Option 1: Install from the Cursor marketplace** 1. Open the [ResolveAI listing](https://cursor.com/marketplace/resolve-ai) and click **Add to Cursor**, or type `/add-plugin resolve-ai` in the Cursor input. 2. Enable the plugin once it installs. 3. Authenticate to your ResolveAI organization when Cursor prompts you. **Option 2: Install from the ResolveAI plugin repo** 1. In the Cursor Dashboard, open Plugins and add a team marketplace, importing this repository: `https://github.com/resolve-ai-oss/resolve-ai-plugins`. 2. Assign the marketplace to the right distribution groups, then install `resolve-ai` from Cursor's marketplace panel. 3. Restart Cursor. The `resolve` MCP server should appear in Settings > MCP. 4. Authenticate to your ResolveAI organization when Cursor prompts you. *** ## Authentication The MCP transport uses OAuth. On first connect, the host (Claude Code, Codex, or Cursor) discovers Resolve OAuth and prompts you to sign in. No API key is needed for normal plugin usage. Not using one of these plugins? See [Resolve MCP Server](/resolve-mcp-server) under Developers for the endpoint, token authentication, and the full tool reference. *** ## 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. | | `create-skill` | Write or tune a skill for the Resolve plugin, encoding workflow guidance rather than tool API details. | | `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 The plugin's skills are built on top of Resolve's MCP tools, which are also available directly to any MCP client. For the full tool reference, live-progress behavior, and usage and billing, see [Resolve MCP Server](/resolve-mcp-server) under Developers. *** ## Where to Go Next * [Admin Plugin](/admin-plugin): companion plugin for administrators who manage Resolve integrations. * [Migrating from the MCP Beta](/migrating-from-the-mcp-beta): switch from the old `/mcp` endpoint and manual setup to the plugin.