How to connect Sentry to Codex

1. 1. Enable Sentry in Metorial

   In your Metorial portal, enable the Sentry MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

2. 2. Add the server and sign in

   The Codex CLI, IDE extension and ChatGPT desktop app share this config.

   Copy

   codex mcp add metorial --url <your-magic-mcp-url>
   codex mcp login metorial

3. 3. Check the connection

   Type /mcp in Codex to see Metorial and its Sentry tools.

• Manage Team: Create, update, or delete a team.
• List Teams: List all teams in the Sentry organization with their members and project assignments.
• Discover Query: Run an ad-hoc query against Sentry's Discover (Events) interface.
• Manage Cron Monitor: List, create, update, or delete cron monitors for tracking scheduled jobs.
• Get Event: Retrieve a specific error event by ID, or list events for an issue.
• Manage Issue Comment: List, create, update, or delete comments (notes) on a Sentry issue.
• Get Organization: Retrieve details about the configured Sentry organization, including quotas, settings, features, and member/project counts.
• Manage Release: Create, retrieve, update, or delete a release.
• List Issues: Search and list issues in the Sentry organization.
• Manage Project: Create, update, or delete a Sentry project.
• List Projects: List all projects in the Sentry organization.
• Get Issue Details: Retrieve detailed information about a specific Sentry issue, including its latest event with stack trace, tags, and contextual data.
• Update Issue: Update a Sentry issue's status, assignment, bookmark state, or other properties.
• List Members: List members of the Sentry organization.
• Manage Alert Rule: List, create, update, or delete issue alert rules and metric alert rules.

• Limit which Sentry tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
• Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
• Type /mcp in the composer to see the connected servers.
• Override the approval behavior for a single Sentry tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Metorial times out at startup

Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.

Long tool calls fail after a minute

The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.