{
  "markdown": "<!--\nCopyright 2026 Resolve AI, Inc.\nSPDX-License-Identifier: Apache-2.0\n-->\n\n<p align=\"center\">\n  <img src=\"./assets/resolve-logo.svg\" alt=\"Resolve logo\" width=\"72\" />\n</p>\n\n<h1 align=\"center\">Resolve AI</h1>\n\n<p align=\"center\">\n  <strong>Machines on call for humans.</strong>\n</p>\n\n<p align=\"center\">\n  AI agents that run your software, so your engineers can get back to building — now inside Claude Code, Codex, Cursor, and Pi.\n</p>\n\n---\n\nResolve is an AI SRE for production. Its agents join every on-call rotation to triage and investigate alerts, work alongside your engineers to get to root cause and fix, and capture the tribal knowledge of your systems along the way — trusted by world-class engineering teams to drive up to **5× faster MTTR**.\n\nThis plugin brings that into your coding agent over MCP: open and steer investigations, ask follow-up questions, pull production context, and turn root-cause findings into pull requests without leaving your editor.\n\n```text\nhttps://app0.resolve.ai/mcp/v2\n```\n\n## Contents\n\n- [How It Works](#how-it-works)\n- [Install](#install)\n- [Migrating from v1](#migrating-from-v1)\n- [Authentication](#authentication)\n- [Skills](#skills)\n- [Live Progress](#live-progress)\n- [Admin Plugin](#admin-plugin)\n- [FAQ](#faq)\n\n## How It Works\n\nAsk your agent to:\n\n```text\nShow me recent Resolve investigations.\nSummarize this investigation: https://app0.resolve.ai/chat/<investigation_id>\nAsk Resolve what changed around the latency alert.\nApply the fix from this Resolve root-cause analysis.\n```\n\nThe plugin connects your agent to Resolve over MCP and installs skills for listing alerts, reading investigations, starting new root-cause analyses, following live progress, asking questions, steering active investigations, reading cited files, and submitting feedback.\n\n## Install\n\n### Claude Code\n\n```text\n/plugin marketplace add resolve-ai-oss/resolve-ai-plugins\n```\n\n```text\n/plugin install resolve-ai@resolve-ai-plugins\n```\n\nRestart Claude Code after installation. `/mcp` should show `resolve` connected.\n\n### Codex\n\n```sh\ncodex plugin marketplace add resolve-ai-oss/resolve-ai-plugins\ncodex plugin add resolve-ai@resolve-ai-plugins\ncodex mcp login resolve\n```\n\nRestart Codex after installation. `/mcp` should show `resolve` connected.\n\n### Cursor\n\nCursor support is still being tested. Unless you are validating Cursor distribution, use Claude Code or Codex today. Treat these steps as the intended install path once marketplace distribution is fully validated.\n\n1. In the Cursor Dashboard, open Plugins and add a team marketplace.\n2. Import this repository:\n\n   ```text\n   https://github.com/resolve-ai-oss/resolve-ai-plugins\n   ```\n\n   Cursor reads `.cursor-plugin/marketplace.json`, which exposes both `resolve-ai` and `resolve-ai-admin`.\n\n3. 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.\n\nFor local testing before marketplace distribution, clone the repository and symlink the Cursor plugin directories into `~/.cursor/plugins/local`, then restart Cursor.\n\nCursor MCP install links and `cursor --add-mcp` install only an MCP server definition, not Resolve's skills — use the plugin marketplace for the full plugin. To re-discover new plugins added to the repository later, re-import the repository URL.\n\n### Pi\n\nPi uses `pi-mcp-adapter` plus a Pi package manifest; it does not read the Claude/Codex/Cursor plugin manifests.\n\n```sh\npi install npm:pi-mcp-adapter\npi install git:github.com/resolve-ai-oss/resolve-ai-plugins\n```\n\n`pi install` loads the skills and Pi guidance extension but does **not** merge MCP servers into your Pi config. Add a `resolve` HTTP MCP server pointing at the [Resolve MCP URL](#other-mcp-clients) to your Pi config (`~/.pi/agent/mcp.json`).\n\nRestart Pi, then run `/mcp reconnect resolve` (or ask Pi to connect Resolve); the first connection opens the browser OAuth flow — no API key needed. Resolve skills appear as Pi commands such as `/skill:overview` and `/skill:ask`.\n\n## Migrating from v1\n\nResolve MCP moved to `/mcp/v2`, with OAuth and the plugin install flow above.\n\n### Claude Code, Codex, or Cursor\n\nIf you previously configured Resolve MCP manually:\n\n1. Remove the old Resolve MCP server entry.\n2. Remove any old `RESOLVE_API_KEY` from your shell profile or host config.\n3. Install `resolve-ai` from the plugin marketplace using [Install](#install).\n4. Sign in with OAuth when prompted.\n5. Restart your host. `/mcp` should show `resolve` connected.\n\n### Other MCP clients\n\nFor MCP clients that do not support this plugin, point the client at:\n\n```text\nhttps://app0.resolve.ai/mcp/v2\n```\n\nThese clients get the same Resolve MCP tools, but not the bundled plugin skills. Authenticate with a `RESOLVE_API_KEY` ([how to generate one](#how-do-i-generate-a-resolve-api-key)) sent as a bearer token. Most hosts take either a static header or a token env var:\n\n```jsonc\n// header-based hosts\n\"resolve\": {\n  \"type\": \"http\",\n  \"url\": \"https://app0.resolve.ai/mcp/v2\",\n  \"headers\": { \"Authorization\": \"Bearer ${RESOLVE_API_KEY}\" }\n}\n```\n\n```toml\n# Codex-style hosts\n[mcp_servers.resolve]\nurl = \"https://app0.resolve.ai/mcp/v2\"\nbearer_token_env_var = \"RESOLVE_API_KEY\"\n```\n\n```jsonc\n// Cursor mcp.json — references env vars as ${env:NAME}, not the bare ${NAME}\n\"resolve\": {\n  \"type\": \"http\",\n  \"url\": \"https://app0.resolve.ai/mcp/v2\",\n  \"headers\": { \"Authorization\": \"Bearer ${env:RESOLVE_API_KEY}\" }\n}\n```\n\n### REST API only\n\nIf you only call the Resolve REST API and do not use MCP, no action is needed.\n\n## Authentication\n\nThe MCP transport uses OAuth. On first connect, Claude Code, Codex, Cursor, or Pi discovers Resolve OAuth from `https://app0.resolve.ai/mcp/v2` and prompts you to sign in.\n\nYou do not need to generate or export `RESOLVE_API_KEY` for normal plugin usage. Identity and access scope come from the OAuth sign-in.\n\nCursor uses a fixed OAuth callback for all MCP servers:\n\n```text\ncursor://anysphere.cursor-mcp/oauth/callback\n```\n\nIf a Resolve deployment whitelists redirect URIs instead of relying only on Dynamic Client Registration, that callback must be registered on the Resolve OAuth app.\n\n## Skills\n\n| Skill            | Use it for                                                                                            |\n| ---------------- | ----------------------------------------------------------------------------------------------------- |\n| `alerts`         | List and filter firing alerts by team, time range, label, severity, or auto-investigation status.     |\n| `ask`            | Ask Resolve a question, either in a new chat or as a follow-up to an existing chat or investigation.  |\n| `apply-fix`      | Translate Resolve's root-cause findings into local code changes and a PR.                             |\n| `chats`          | List recent Resolve chats and see which ones are still running.                                       |\n| `demo`           | Run a guided tour of Resolve using live data from the connected org.                                  |\n| `feedback`       | Capture a verdict on an investigation, chat answer, or the product when work wraps up, and submit it. |\n| `help-resolve`   | Explain Resolve and route the user to the right workflow.                                             |\n| `investigate`    | Open an existing Resolve investigation or start a new RCA from a problem description.                 |\n| `investigations` | List and filter recent investigations by team, run type, use case, and time range.                    |\n| `overview`       | Get a compact snapshot of investigations, alerts, and chats.                                          |\n| `prod-context`   | Pull production context before implementing a risky code, infra, config, or migration change.         |\n| `steer`          | Send a finding, hypothesis, or directive into an active Resolve investigation.                        |\n\nThe underlying MCP tools include `get_investigation`, `start_investigation`, `ask`, `get_chat`, `list_chats`, `list_investigations`, `list_alerts`, `steer_investigation`, `read_file`, `upload_attachment`, and `submit_feedback`.\n\n## Live Progress\n\nSome Resolve operations are long-running. `ask`, `start_investigation`, and `steer_investigation` may return a `stream_command`, which is a self-contained `curl` command for following live progress.\n\nThe host agent runs that command in the background and reads stdout until the operation completes. The command carries a short-lived scoped watch token, so no API key is needed.\n\n## Admin Plugin\n\nThis marketplace also ships `resolve-ai-admin`, a companion plugin for administrators who manage Resolve integrations.\n\n| Skill                | Use it for                                                                                                 |\n| -------------------- | ---------------------------------------------------------------------------------------------------------- |\n| `create-integration` | Route a new data source to the right setup path: SaaS REST API, satellite-backed config, or UI/OAuth flow. |\n| `debug-integration`  | Diagnose or explain a failing or quiet integration.                                                        |\n| `satellite-configs`  | Edit a satellite Helm `values.yaml` for satellite-backed integrations and networking.                      |\n\n`resolve-ai-admin` has no MCP server of its own. It reuses the `resolve-ai` plugin's `/mcp/v2` connection and hands off to `resolve-ai:ask`, so install `resolve-ai` first.\n\n```text\n/plugin install resolve-ai-admin@resolve-ai-plugins\n```\n\nFor Cursor, install `resolve-ai-admin` from the same team marketplace after `resolve-ai`. Keep it optional unless every developer in the group manages Resolve integrations.\n\n## FAQ\n\n### How do I generate a Resolve API key?\n\nIf you use the plugin in Claude Code, Codex, Cursor, or Pi, you don't need one — sign-in is handled by OAuth (see [Authentication](#authentication)), and normal plugin usage never needs an API key.\n\nFor MCP-only clients or direct REST API access, create a personal API token in Resolve:\n\n1. Sign in to Resolve and open **Personal API Tokens** at `https://app0.resolve.ai/personal-tokens`.\n2. Click **Create Personal Token** and copy the value — it's shown only once, so if you lose it you'll need to generate a new one.\n\nUse that token as your `RESOLVE_API_KEY`.\n\n### Do I need to clone the repo?\n\nNo for Codex and Claude Code — both add the GitHub marketplace directly. For Cursor, no-clone install requires the public Cursor Marketplace or a team/private marketplace; local testing still uses a checkout.\n\n### Does `resolve-ai-admin` replace `resolve-ai`?\n\nNo. `resolve-ai-admin` is optional and requires `resolve-ai` to be installed alongside it.\n",
  "bytes": 10835,
  "sha": "db648be10008f72fe73efa2f8f6ebcdf6d657c0d55b503f0101eb36b7f19459d",
  "repo_slug": "resolve-ai-oss/resolve-ai-plugins",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_resolve_ai_oss_resolve_ai_plugins_resolv_79f799a4/readme"
}