MCP Gateway · Claude Cowork
Connect Sentry to Claude Cowork
Reliability reporting is slow, careful work: dozens of Sentry projects, a handful of bad releases, and a document at the end. Handing it to Cowork lets one long task do the counting, the reading and the writing. Speakeasy screens every prompt in that task through agent hooks, and OTLP export records whose session it was.
- Category
- Developer tools
- Tools
- 22
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
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.
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.
Set up
Add Sentry to Claude Cowork in 4 steps
- 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.
- 02
Choose who can use Sentry
Give teams the
mcp:connectscope on the Sentry server through team access or a role. Claude Cowork connects to the Sentry server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Sentry from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Sentry
Write the weekly reliability report
Cowork goes through every Sentry project, counts the week's error events, picks out the issues that grew fastest, and drafts the report engineering leadership reads on Monday.
Review a release after it ships
For each release in the past sprint, Cowork lists the new issues it introduced and asks Seer for a root cause on the largest, then writes a review document.
Audit project ownership
Compare every Sentry project with the current team list, flag projects assigned to teams that no longer exist, and prepare the ownership changes for approval.
Tools
22 tools
Each Sentry tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does Cowork get more Sentry access than the person running it?
Can personal Claude accounts use Sentry in Cowork?
How do Claude Cowork users get Sentry?
Are Sentry calls from Claude Cowork logged?
Connect more