Commands
/sentry:seerAsk a question about what Sentry is seeing right now — which errors are turning up most, which ones are hitting the most people — and get the answer in words instead of going and reading a dashboard.
PLUGIN / GETSENTRY
Sentry SDK Setup & Debugging
Hands an assistant Sentry's own installation steps for whatever language an app happens to be written in, plus the ones for dealing with the errors that follow.
Gets Sentry running in any app, whatever the language, proves an event arrives, then fixes recorded errors and decides who gets alerted.
Install Sentry, fix what it records, route the alert.
Sentry is where an app's crashes go so that somebody sees them. Getting it in, and then acting on what it collects, is what these guides are for — three jobs in particular:
- install Sentry in an app and confirm that a real event arrives
- take an error Sentry has already recorded and change the code so it stops happening
- decide who is told about a new problem, and whether by email, Slack, PagerDuty or Discord
Half of it is about sending more.
The 8 guides divide three ways:
- 2 — installing the SDK
- 4 — choosing what else to send
- 2 — once it is in production
Every language is covered by one entry, which works out what the app is built on and installs for that.
A Sentry project, and the connection to it.
These guides assume a Sentry project is there, or soon will be: the setup guides finish by proving that something arrived, and the guides that act on errors read them out of a project you own.
So two things must be in place before anything is reported:
- a Sentry project, which the first-run guide can set up for you
- the connection between the assistant and that account, which the plugin sets up itself
One source, a separate plugin built per assistant.
Every guide lives in this one repository, and yet the plugin for any single assistant is not this repository. A build step turns the material into one plugin per tool it supports:
- Claude Code
- Cursor
- Codex
- Grok
Each of those is generated and kept in its own repository, so what lands in an assistant is built out of this material rather than being it.
What gets installed: 8 skills, 1 command, 2 agents, 1 MCP server
Skills
Where to start when nothing is reporting yet. One entry looks at what is already in place and, for a new project, goes end to end: creates the project in Sentry, adds the SDK and checks that real data arrives. The other detects the platform and switches on whatever comes next, from tracing and logs to session replay, scheduled-job check-ins and AI monitoring.
sentry-get-startedThe front door to Sentry, a service that catches the errors your software runs into and shows where they came from. On a new project it sets Sentry up and proves a real error arrives; on one that already has it, it points you to the right next step.sentry-instrumentGets Sentry recording one more kind of information about your app — or its very first error on a new install — and does not call it finished until a real example has turned up in Sentry.
For when errors already arrive and the question is what to add next: a shared OpenTelemetry pipeline branched off into Sentry, and pictures of an Apple app's screens taken on every pull request. Two more make the data easier to act on: the source maps and debug files that turn a garbled stack trace back into the source you wrote, and release tags that show which version and which commit brought a problem in.
sentry-fix-stack-tracesWhen Sentry's error reports point at scrambled code instead of your own file names and line numbers, this gets the missing lookup files uploaded from your build so the next error reads properly.sentry-otel-exporter-setupSeveral services already send their telemetry into one shared OpenTelemetry pipeline — this branches that stream off to Sentry, each service landing in its own project.sentry-setup-releasesMakes every error in Sentry say which version of your app it came from, which code changes went into that version, and which change most likely caused it.sentry-snapshots-cocoaTakes pictures of an Apple app's screens on every pull request and sends them to Sentry, so a change that alters how something looks is spotted before it ships.
Everything that comes after a release. One entry starts from an error already sitting in Sentry, pulls its full history and changes the code behind it, then closes it with the commit that fixes it. The other settles which interruptions are worth making and who gets them.
sentry-create-alertSentry spots a problem at two in the morning; this is where you decide who hears about it and how — by email, Slack, PagerDuty or Discord.sentry-debug-issueOne error report in Sentry, carried all the way from “something is broken” to a shipped fix: the cause found in your own code, a test that reproduces it, and the report closed by the change itself.
Agents
Neither of these two touches your own code. They write and repair the guides themselves: hand one a platform, or a guide that has fallen behind, and it works out the research for itself. A skill carries out a job you have already named; these take the job of keeping the collection true.
Starts from nothing for a platform that has no guide yet: reads Sentry's documentation for it, clones that SDK's source to confirm the options it is about to write down really exist, and opens a pull request with the finished guide and its reference pages.
For a guide that has drifted from the SDK it describes: it finds what changed in the SDK, confirms the new names in that project's own code, and rewrites only the parts that no longer hold.
What the assistant can look into on your Sentry account.
CONNECTS TOYour Sentry account
The plugin wires this up while it installs; nothing else has to be connected.
The first time it is used, it asks you to sign in to Sentry.
What it lets the assistant do.
search errors
analyse performance
triage issues
read Sentry's documentation
manage projects
Every tool the server offers is listed on its own page:Sentry MCP server
https://mcp.sentry.dev/mcp?utm_source=plugin02One line in a terminal, then name your platform:
INSTALL
One line in a terminal, then name your platform:
“add Sentry to my Next.js app.”
Paste one line in a terminal
npx @sentry/agent-plugin install