Best for
- Developers using coding agents like Claude Code and Cursor
- Workflows requiring interaction with Sentry for debugging
S
Sentry MCP Server
Official
Sentry's official MCP server for interacting with Sentry via LLMs.
GitHub source repository ↗
60FMRS · C
Sentry's official MCP server focused on developer debugging scenarios, interacting with Sentry API via remote or stdio transports. Note permissions and external LLM dependencies.
Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality. This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools. It's based on Cloudflare's work towards remote MCPs.
Tools
The tool list has not been reviewed yet.
Setup
- Ensure Node.js is installed. 2. Run the server using npx, providing a Sentry User Auth Token via command-line argument or environment variable. 3. For remote use, configure MCP clients to point to https://mcp.sentry.dev/mcp. 4. For AI-powered search tools, configure an LLM provider (e.g., OpenAI) with API key.
claude_desktop_config.json
{
"mcpServers": {
"sentry": {
"command": "npx",
"args": [
"@sentry/mcp-server"
],
"env": {
"SENTRY_ACCESS_TOKEN": "your-token",
"EMBEDDED_AGENT_PROVIDER": "openai",
"OPENAI_API_KEY": "sk-..."
}
}
}
}
Fit and risk
Not for
- Not suitable for general-purpose MCP servers needing full Sentry functionality
- Not suitable for users without a Sentry account or self-hosted instance
Required permissions
- Requires a Sentry User Auth Token with scopes: org:read, project:read, project:write, team:read, team:write, event:write
Risks and side effects
- AI-powered search tools rely on external LLM providers, potentially exposing data to third parties
- Automated code review tools may produce false positives and should not be blocking requirements
Troubleshooting
- Check SENTRY_ACCESS_TOKEN is set and valid
- For AI search tools, confirm EMBEDDED_AGENT_PROVIDER and corresponding API key are set
- For self-hosted, verify --host parameter is correct, add --insecure-http if needed
- If OAuth flow has issues in MCP Inspector, try using localhost instead of 127.0.0.1
Use cases
Debugging Sentry errors and exceptions
Viewing and analyzing issues and traces
Querying events and performance data
Supported clients
ClaudeFull support
CursorFull support