MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Paste into claude_desktop_config.json:
{
"mcpServers": {
"sentry-mcp": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server"
],
"env": {
"SENTRY_ACCESS_TOKEN": "<SENTRY_ACCESS_TOKEN>"
}
}
}
}Run in a terminal:
claude mcp add sentry-mcp --env SENTRY_ACCESS_TOKEN=<SENTRY_ACCESS_TOKEN> -- npx -y @sentry/mcp-server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"sentry-mcp": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server"
],
"env": {
"SENTRY_ACCESS_TOKEN": "<SENTRY_ACCESS_TOKEN>"
}
}
}
}Transport: stdio - Runs locally over stdio. Your client launches the process itself; you need the matching runtime installed (Node for npx, uv for uvx, Docker for docker run).
Auth: requires credentials - replace the <PLACEHOLDER> environment values in the config with your own keys (see the vendor's docs).
https://wingmanprotocol.com/mcp.