Skip to main content
Book a demo

Connect Sentry to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Sentry to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork 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 Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Sentry’s 16 tools show up in Claude Cowork’s own tool list.

    Claude Cowork 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 Cowork

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

Tools

16 Sentry tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork 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 Cowork

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork 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)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination