Skip to main content
Back to the Sentry MCP server

MCP Gateway · Codex

Sentry icon

Connect Sentry to Codex

When Codex scaffolds a new service, it can set up the Sentry side too: the project, the DSN and the team that owns it. Later it can download the files attached to a crash and debug from them. Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.

Category
Developer tools
Tools
22
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Sentry from Codex

    The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Sentry

Create a project for a new service

Ask Codex to create the Sentry project for the service it just scaffolded, assign it to the owning team, and write the returned DSN into the service's configuration.

find_teamscreate_project

Add a DSN for another environment

When a service gains a staging deployment, Codex lists the project's existing DSNs and creates an additional one, then updates the environment config to use it.

find_dsnscreate_dsn

Debug from a crash attachment

Download the attachments on a Sentry event, such as a log file or crash dump, and let Codex read them alongside the code to find the failing path.

get_event_attachment

Tools

22 tools

Each Sentry tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex

The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Codex

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Can I stop Codex from creating Sentry projects?
Yes. Each of the 22 Sentry tools can be allowed or denied per team and role at the MCP Gateway, so Codex can read DSNs and events without create_project or create_team.
Is Sentry activity from Codex attributed to a developer?
Yes, once an [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
How do Codex users get Sentry?
An admin adds Sentry from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Sentry tools their access allows.
Are Sentry calls from Codex 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.