Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Sentry to Claude Code

Let Claude triage, resolve, and assign issues in Sentry. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Sentry to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Sentry, you add a Sentry MCP server: a small hosted service that exposes Sentry's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Sentry account. No API keys pasted into config files.

claude mcp add --transport http sentry https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Sentry once connected?

Full read-write Sentry access lets Claude resolve or ignore an issue, assign it to a teammate, set its priority, bookmark it for follow-up, and update an alert rule once you approve. The triage that used to mean tab-switching happens where the errors already live, alongside the stack trace.

  • Resolve, ignore, or reopen an issue after you confirm the fix
  • Assign an issue to a teammate or team
  • Set the priority on an issue so the right work surfaces first
  • Bookmark an issue or mark it seen to keep triage organized
  • Create or update an alert rule for a service
  • Mute or adjust a noisy alert during an incident

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Sentry access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Sentry API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Sentry changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Sentry connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Sentry connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Sentry account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Sentry's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Sentry?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Sentry account it signs in with. Revoking access is one click in Sentry.

More on the Sentry connector

Sentry connector for claude.aiDatadog + Claude CodeGitHub + Claude CodePagerDuty + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us