getsentry sentry-mcp
OFFICIALLABSCO SUMMARY
Eleven skills ship in the repository, and the split runs more to type than to count: five openspec-* skills (explore, propose, apply-change, sync-specs, archive-change) run a spec-first change workflow for the codebase; mcp-audit and mcp-qa check a tool's protocol compliance and QA it against a real agent client; testing-guidelines and logging-observability set the team's own conventions — the latter enforcing that 4xx errors are never sent to Sentry while 5xx errors always are; and create-pr and skill-creator are, by their own descriptions, aliases that redirect elsewhere rather than skills in their own right.
This is for someone contributing to sentry-mcp's own codebase — opening a PR, adding an MCP tool, or writing a spec-driven change — not for someone who wants their agent to look up a Sentry issue. That second use case is served by the MCP server this repository builds, reachable directly at mcp.sentry.dev or self-hosted via npx @sentry/mcp-server, and it doesn't route through any of these eleven skills.
READ THE FULL ANALYSIS
Two of the eleven point outside this repository entirely. create-pr and skill-creator each describe themselves as an alias — "Redirects to the canonical PR writing workflow" and the equivalent for skill authoring — for pr-writer and skill-writer in a separate getsentry/skills repository, pulled in by the @sentry/dotagents install step in this repo's own setup instructions. Install this package on its own and those two names still appear, aliasing to skills we have not independently reviewed.
The MCP server itself is the part with real requirements. A Sentry user auth token is required for the stdio transport, and the AI-powered search tools (search_events, search_issues) additionally need an OpenAI, Azure OpenAI, Anthropic, or OpenRouter key — without one, those specific tools go unavailable but the rest of the server still works. Self-hosted Sentry instances can turn off unsupported tools, such as Seer, with a --disable-skills flag.
ALSO IN THIS PACKAGE
sentry-mcp
Sentry error tracking and performance monitoring via MCP
sentry-mcp-experimental
Sentry MCP with experimental features enabled
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when
sentry
Official Sentry MCP server for investigating issues, error reports, traces, and performance monitoring data from AI coding agents.
http · https://mcp.sentry.dev/mcp/sentry/mcp-server?experimental=1sentry-dev
http · http://localhost:5173/mcp/sentry/mcp-server?experimental=1sentry
Official Sentry MCP server for investigating issues, error reports, traces, and performance monitoring data from AI coding agents.
http · https://mcp.sentry.dev/mcpWHAT'S INSIDE
11 showing · 11 totalNothing else to set up — install it and go.
create-pr
logging-observability
Reviews code against the one error-handling rule this project treats as sacred: a mistake the user can fix should never raise an alert, and a genuine server failure always should.
mcp-audit
Checks an MCP server against the official rules of the protocol it claims to speak and reports every place it falls short — what it advertises, what its tools really do, how it carries traffic and handles logins.
mcp-qa
The check that has to happen after you change one of Sentry's AI-assistant tools: ask it a real question against a live Sentry account and judge the answer it gives back.
openspec-apply-change
Works down the task list of a plan that was already written, building each step and ticking it off as it goes, and stopping to ask whenever a task is too vague to act on.
openspec-archive-change
Closes out a finished piece of work: checks that nothing was left undone, offers to carry what it decided into the project's standing documents, then files the whole folder away under today's date.
openspec-explore
A thinking partner for the stage before anything is decided: it reads how the existing code actually works, lays out the options and what each one costs, and helps a fuzzy idea harden into a plan worth writing down.
openspec-propose
On a project where every piece of work is planned in writing before any code, this writes that plan from one description of what you want: what and why, how it will be built, and the steps.
openspec-sync-specs
Merges what one piece of work changed into the project's master requirement documents, applying only the additions, edits, renames and deletions it listed and leaving the rest of the text alone.
skill-creator
testing-guidelines
A short rulebook for writing tests here: fake any outside service, base your test data on real recorded responses, never fix a bug without a test that would have caught it, and give every command or function a user can reach at least one test.
HOW TO GET IT
npx skills add getsentry/sentry-mcpnpx skills add getsentry/sentry-mcp --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
/plugin marketplace add getsentry/sentry-mcp/plugin install sentry-mcp@sentry-mcp/plugin install sentry-mcp-experimental@sentry-mcpTyped inside the agent's own prompt, not in a terminal. The marketplace is called sentry-mcp, which is the part after the @.