Skip to main content
Book a demo

Connect Sentry to Claude

Give Claude governed access to Sentry’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Sentry to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Sentry in Runlayer

    Add Sentry from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Sentry’s 16 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Sentry

    Sign in the way Sentry requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Sentry from Claude

    Sentry’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

16 Sentry tools in Claude

Runlayer policy decides which of these Claude users can call. 4 read data only.

  • Analyze issue with seer

    Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes.

  • Execute Sentry tool

    Execute an available Sentry MCP tool discovered through search_sentry_tools.

  • Find dropped events

    Find events dropped before they were stored in Sentry — ground-truth data-fidelity information about what was and wasn't captured.

  • Find organizations

    Find organizations that the user has access to in Sentry.

  • Find projects

    Find projects in Sentry.

  • Get Sentry resource

    Fetch a Sentry resource by URL, or by resourceType plus resourceId.

  • Search errors

    Search Sentry error events: exceptions and crashes with stack traces.

  • Search events

    Search Sentry events and replays.

See all 16 Sentry tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Sentry call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination