Sentry MCP server
Triage issue state and release metadata with Arc0’s Sentry tools. The current outputs focus on structural information and exclude error messages and stack traces. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Sentry
A release triage pass can begin with sentry.list_projects and sentry.list_releases to identify the project and recent version metadata. sentry.list_issues then selects issues using Sentry query syntax. An empty query includes resolved issues, so use explicit conditions when the question concerns only unresolved work.
sentry.get_issue provides status, assignee IDs, and event counts. sentry.get_latest_event adds the latest event’s ID, platform, and timestamp, or no event when none remains. These outputs can establish recency and ownership, but they do not include messages, exception details, or stack frames. An agent should not claim to have diagnosed a stack trace from these tools.
When the next step is agreed, sentry.update_issue can change the status or assign a known user or team ID. The change may notify assignees and subscribers. Unassignment is not exposed. Read the issue afterward to confirm the result, especially if the update response was lost. Keep the connected organization and region in mind when comparing issue IDs from another account.
Official MCP reference: Sentry documentation.
Agent workflows for Sentry.
Find a project’s issues
Use sentry.list_projects and sentry.list_issues to narrow the triage queue with Sentry query syntax.
Inspect issue state
Use sentry.get_issue for status, assignee IDs, and event counts before deciding on a change.
Check event recency
Use sentry.get_latest_event for the latest event ID, platform, and timestamp without stack content.
Assign or resolve an issue
Use sentry.update_issue for a reviewed status or assignee change, then sentry.get_issue to verify it.
6 Sentry actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- sentry.list_projectsList projects
Use when you need project IDs and platforms in the connected Sentry organization before narrowing issue searches. Do not use for issue search; use list_issues.
- sentry.list_issuesList issues
Use when triaging errors in the connected organization. Search with Sentry query syntax; an empty query includes resolved issues. Continue with nextCursor until null.
- sentry.get_issueGet issue
Use when checking an issue’s status, assignee IDs and event counts, including reading back an uncertain update before retrying. Do not use for event or stack content.
- sentry.get_latest_eventGet latest event
Use when checking the latest event’s ID, platform and timestamp for an issue. Uses one compact event; returns null if none remains. Do not use for messages or stack traces.
- sentry.list_releasesList releases
Use when identifying recent release versions and new issue counts for a project. Filter query by a version substring; author and commit personal data are omitted. Do not use to create or deploy releases.
write
1Create and change things. Allow, or ask the user first.
- sentry.update_issueUpdate issue
Use when changing issue status or assigning user:ID/team:ID. Changes may notify assignees and subscribers. Do not use to unassign (unsupported). After an uncertain result, read the issue before retrying.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to Sentry.
Connect the intended Sentry account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- sentry.update_issue: require approval
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Sentry connects.
Connect Sentry using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Sentry with your AI client.
Sign in to Arc0 and connect Sentry in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Sentry with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingSentry with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSentry with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingSentry with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSentry with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSentry with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More developer tools apps.
Sentry and Arc0, answered.
Is there an official Sentry MCP server, and how does Arc0 differ?
Yes. Sentry operates an official MCP service. Arc0’s current Sentry tools expose structural issue, event, and release metadata through REST; they do not expose stack-trace analysis.
Which permissions does Arc0 need for Sentry?
Use a bearer API token with org:read, event:read, event:write and project:read capabilities. The connection pins one organization and a supported US or DE region. This version does not offer OAuth or arbitrary self-hosted Sentry origins.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Arc0 stores the token encrypted without a refresh flow. Disconnect removes local access. Revoke the token in Sentry to invalidate its provider-side access, and reconnect with a replacement if it expires.
What happens with rate limits or errors?
Sentry applies API rate limits. Arc0 surfaces throttling and permission failures rather than returning an empty issue list. After an uncertain update, read the issue’s current state before trying again.
What is the availability of these Sentry tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Sentry into your agent.
Sentry MCP server: 6 actions including list projects, list issues, get issue. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Sentry and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Sentry.