Integration · Developer tools

Connect Claude & ChatGPT to Sentry

Ask your AI what is breaking in production and get the answer straight from Sentry. It can list unresolved issues, walk through the stack trace of an event, check a release's health and spot cron jobs that missed a run. When you are ready, it can resolve, ignore or assign issues for you.

Connect Sentry free

Free plan, no credit card. Takes about a minute.

Try asking

“What are the top unresolved errors in production over the last 24 hours?”
The AI runs list_issues with a Sentry search like is:unresolved in the production environment and ranks the results by event count.
“Explain issue WEB-3F2 and show me where it fails.”
It looks up the short ID, fetches the recommended event and walks you through the stack trace, tags and request context.
“How healthy is release 2.14.0, and what shipped in it?”
It reads the release's health, adoption and new issue counts, then lists the commits and deploys for that version.

What your AI can do

Issues and stack traces

Search issues with Sentry's own query syntax and open any event with its stack trace, tags, request and user context. The AI can also read Seer's suggested fix for an issue.

Releases, deploys and crons

Check release health and adoption, list commits and deploys, and follow cron monitor check-ins to catch missed runs.

Triage from the chat

Resolve, ignore, bookmark or assign issues without opening Sentry. Every other Sentry tool only reads data.

“Did any cron jobs miss a run last night?”
It lists your cron monitors and their recent check-ins and points out missed or failed runs.
“Which browsers are hit by this checkout error?”
It pulls the browser tag breakdown for the issue, with a count for each value.
“Assign these three issues to Maria and mark the old one as resolved.”
It finds Maria in the member list and updates the issues by ID with the new assignee and status.

28 tools for Sentry

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

find_event_by_idFind which project and issue an `event_id` belongs to in the organization.
get_cron_monitorGet one cron monitor by `monitor_id_or_slug`, with its schedule and status.
get_eventGet one event by project and `event_id`, with stack trace, tags, request and user context.
get_event_statsGet event counts per project for the organization: `field` (e.g. sum(quantity)), `category` (error, transaction...), `stats_period` and `interval`.
get_issueGet one issue by ID, with title, culprit, status, event counts, users affected and first/last seen.
get_issue_autofixGet the state and suggested fix of Sentry's AI (Seer) analysis for an issue by `issue_id`.
get_issue_by_short_idLook up an issue by its short ID (e.g. PROJECT-1A2) and get its numeric ID and project.
get_issue_eventGet one event of an issue by `issue_id` and `event_id` (use latest, oldest or recommended), with stack trace, tags and context.
get_issue_tagGet the breakdown of one tag (e.g. browser, release, environment) for an issue by `issue_id` and `tag_key`.
get_organizationGet one organization by `company_id_or_slug`.
get_projectGet one project by organization slug and `project_id_or_slug`.
get_releaseGet one release by `version`, with health, adoption and new issue counts.
list_cron_checkinsList the recent check-ins of a cron monitor by `monitor_id_or_slug`, to see missed or failed runs.
list_cron_monitorsList cron monitors in an organization, filtered by `project`, `environment` or `owner`.
list_environmentsList the environments (e.g. production, staging) in an organization.
list_issue_eventsList the events (individual occurrences) of an issue by `issue_id`, optionally filtered by `query`, `environment` or time range.
list_issue_tag_valuesList all values of one tag for an issue by `issue_id` and `tag_key`, with counts.
list_issuesList issues in an organization using Sentry search in `query` (e.g. is:unresolved level:error), with `project`, `environment`, `stats_period` and `sort`. Use to find the top or newest errors.
list_membersList organization members, optionally filtered by `query` (e.g. email). Use to find a member to assign issues to.
list_organizationsList the Sentry organizations you can access, with their slugs. Use the slug in the other tools.
list_project_eventsList recent error events in a project, optionally within a time range or `stats_period`.
list_projectsList projects in an organization, optionally filtered by `query`.
list_release_commitsList the commits included in a release by `version`.
list_release_deploysList the deploys of a release by `version`, with environments and dates.
list_releasesList releases in an organization, filtered by `project`, `environment` or `query`.
list_teamsList teams in an organization, optionally filtered by `query`.
list_user_feedbackList feedback that end users submitted in a project.
update_issuesVisible to othersUpdate issues in a project: pass issue `id`(s) and set `status` (resolved, unresolved, ignored), `assigned_to`, `is_bookmarked` or `has_seen`. Without `id` it applies to every matching issue in the project, so always pass IDs.

Set up in three steps

1
Pick the app
Create a free PipMCP account and choose Sentry from the app list.
2
Paste your key
Paste a Sentry auth token. In Sentry, go to User settings > Personal Tokens, click Create New Token, choose the scopes you want the AI to have and copy the token.
3
Add the link to your AI
You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:
Click your name, then Settings › Connectors › Add custom connector. Paste your link as the Remote MCP server URL. Switch it on from the + menu in a chat.

Questions

What can the AI do in Sentry?

It can read organizations, projects, teams, members, environments, issues, events, releases, cron monitors, user feedback and event stats. It can find the issue an event ID belongs to and read Seer's autofix analysis. The only tool that changes anything is update_issues, which sets status, assignee, bookmark or seen state.

Does the AI see my Sentry API key?

No. You paste your Sentry auth token into PipMCP once. It is encrypted at rest, never shown to the AI and never shown again after you save it. The AI only gets the results of the tools you have switched on.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can leave update_issues off and keep the connection read-only. You can also require approval before the AI updates issues. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT, open Settings › Apps & Connectors › Advanced, turn on Developer mode and add your PipMCP link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector) and in Cursor.

What does it cost?

PipMCP has a free plan, and you do not need a credit card to start. Paid plans are billed per completed task. You connect your own Sentry account, so anything Sentry charges is between you and Sentry.

Which scopes should my Sentry token have?

Give the token only what the AI needs. For lookups, read access to your organization, projects and issues is enough. If you want the AI to resolve or assign issues, the token also needs write access to issues. The token's scopes and the tools you switch on in PipMCP both limit what the AI can do.