Skip to main content
Back to the Sentry MCP server

MCP Gateway · Claude

Sentry icon

Connect Sentry to Claude

Product managers want to know how a feature is holding up in production without reading stack traces. Claude can tell them which Sentry project covers it, how often it errors and which browsers or releases are hit. Access runs through the Speakeasy MCP Gateway, where roles decide which Sentry servers and tools a product manager can use.

Category
Developer tools
Tools
22
Authentication
OAuth
Claude
Web, desktop and mobile

Behind the MCP Gateway

Run Sentry MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Sentry call inspected and logged.

Deploy on MCP Gateway

Before you start

What Sentry needs first

Any Sentry user with access to the needed organizations and projects does the Sentry side of the setup.

  • You create nothing in Sentry before adding the server.
  • Users can only reach what their Sentry account already can.
Full Sentry setup guide in the docs

Set up

Add Sentry to Claude in 4 steps

  1. 01

    Add Sentry from the catalog

    An admin finds Sentry in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Sentry uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Sentry

    Give teams the mcp:connect scope on the Sentry server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Sentry to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Sentry from Claude

    The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Sentry needs its own OAuth grant, so each person connects it once. Until they do, Sentry calls fail while the rest of the gateway keeps working.

    From then on, Sentry's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Sentry

Check a feature's error rate

Ask Claude to find the project behind a feature and count its error events over the past week, then compare the number with the week before launch.

find_projectssearch_events

See who an issue affects

For a known issue, get the breakdown of affected browsers, devices and releases, and decide whether it belongs on this sprint's roadmap.

get_issue_tag_valuesget_sentry_resource

Explain an issue in plain language

Paste a Sentry issue link and have Claude explain what is failing and how often, so you can write a clear note for stakeholders who don't read Sentry.

get_sentry_resourcesearch_issues

Tools

22 tools

Each Sentry tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.

whoami

Identify the authenticated user in Sentry.

find_organizations

Find organizations that the user has access to in Sentry.

find_teams

Find teams in an organization in Sentry.

find_projects

Find projects in Sentry.

find_releases

Find releases in Sentry.

get_issue_tag_values

Get tag value distribution for a specific Sentry issue.

See all 22 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.

Tool logs

Gateway

Every Sentry call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Sentry tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Sentry can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can product managers use Sentry in Claude without changing issues?
Yes. Each Sentry tool can be allowed or denied per team and role at the MCP Gateway, so a product role can search issues and events without update_issue.
Can Claude prompts about Sentry be blocked?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do Claude users get Sentry?
An admin adds Sentry from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Sentry tools their access allows.
Are Sentry calls from Claude logged?
Yes. Sentry calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Sentry in other clients

AI everywhere.

Control here.