Integration
Claude Code + Sentry
With Sentry's official MCP, your agent reads real production errors (issues, stack traces, events) and cross-references them with your local code, so diagnosis stops being copying and pasting traces.
Updated 2026-07-27
What you can do
| Action | What it is for |
|---|---|
| Search issues | Find the errors that affect users the most. |
| Read an issue's detail | Bring the full stack trace into the agent's context. |
| List projects | Work on the right project when you manage several clients. |
| Query events | See the frequency and context of a failure over time. |
How to connect it
- 01Have access to the project in Sentry with read permissions.
- 02Add Sentry's official MCP server to your client following its documentation.
- 03Authorize with your Sentry account.
- 04Test by asking for the most frequent issues of the last week.
Agency use case
From the production error to a proposed fix
- 1.You ask the agent for the project's most frequent error.
- 2.It brings in the issue and its stack trace through the MCP.
- 3.It cross-references the trace with the local repo's files and finds the cause.
- 4.It proposes the fix and you review it before applying it.
What you will trip over
- Stack traces can carry user data. Watch what context goes to the agent if you handle sensitive information.
- Read access is enough to diagnose: you don't need write permissions in Sentry.
- Confirm the project before diagnosing when you manage several clients.
Other integrations
FAQ
Frequently asked questions
Does it work if my app isn't JavaScript?+
Yes. Sentry covers many languages and the MCP exposes the issues the same way, regardless of the app's stack.