Servers / Sentry
Install Sentry MCP in Cursor
Direct answer
Add Sentry's remote MCP with url https://mcp.sentry.io/mcp in Cursor's mcp.json. Reload, sign in, and pick the org. Then paste an issue URL or ask for unresolved errors on this project. If that path 404s, try https://mcp.sentry.io as older client snippets did, and match Sentry's current docs.
Cursor mcp.json
Paste this into ~/.cursor/mcp.json (global) or.cursor/mcp.json (this repo). Merge it with servers you already have. Primer: how Cursor loads MCP.
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.io/mcp"
}
}
}MCP endpoint: https://mcp.sentry.io/mcp. Source: Sentry MCP.
What it is
Sentry MCP is issues, events, and traces. The agent can go from a stack frame to the file it is already editing, instead of you screenshotting the Sentry UI.
The problem it solves
The error is in Sentry. The fix is in Cursor. Without the MCP those stay two windows.
Install steps
- Add the server. url https://mcp.sentry.io/mcp on a sentry entry.
- Authorize the org. OAuth, then confirm the project the agent may read.
- Open an issue. Paste a Sentry issue URL and ask for the root cause against this repo.
A prompt that uses it
Fetch the latest unresolved Sentry issue for this project, open the top stack frame in this repo, and propose a fix that does not hide the error.
If it will not connect
Org mismatch and missing project access are common. If /mcp fails, Sentry's older public URL was https://mcp.sentry.io. Use whichever their current docs show.
FAQ
What URL does Sentry MCP use?
https://mcp.sentry.io/mcp in current Streamable HTTP setups. Confirm against Sentry's MCP docs if install fails.
Can it resolve issues?
If the grant allows writes. Reading events is enough for most coding sessions.
Does this send my code to Sentry?
The MCP reads Sentry. Cursor still sends prompts to the model you picked. Those are separate paths.
Why not just paste the stack trace?
You can. The MCP helps when you want the agent to search issues or follow linked events without a paste.
