What it does & operational scope
Sentry MCP Server connects developer assistants directly to live application monitoring data. Supported through both local stdio and hosted SSE endpoints at sentry.dev, it allows agents to search recent unresolved issues, inspect full stack traces with local variable state, review user telemetry breadcrumbs, and identify regression releases without leaving the code editor.
Sentry MCP Server is an open-source Model Context Protocol server developed by Sentry under FSL-1.1 that connects AI code editors directly to production error stack traces and breadcrumb telemetry.
Your AI coding agent requires live access to Sentry tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "sentry": { "command": "npx", "args": ["-y", "@sentry/mcp-server@latest", "--access-token=<SENTRY_ACCESS_TOKEN>"] } }}Exposed tool endpoints & primitives
Discovered MCP Tools
3 Tools Readylist_issues🟢 Read-Only (Safe)Retrieve unresolved production error issues sorted by event frequency
get_issue_details🟢 Read-Only (Safe)Read full stack trace, exception type, and client breadcrumb records
list_project_events🟢 Read-Only (Safe)Query recent runtime exception events across production deployments
Scopes, secret storage, and sandbox boundaries
Limit Sentry user token permissions to read:org and read:issues. Do not grant admin or project modification scopes.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Sentry MCP Server from the last 7 days"list_issues({ query: "Sentry MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Sentry MCP Server"list_issues_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Pulls real production crash context directly into IDE prompts for instant bug reproduction.
+ Includes local variable dumps and breadcrumb trails that pinpoint exact failures.
+ Official implementation maintained directly by the Sentry engineering team.
− Unsanitized exception frames and HTTP request payloads can leak sensitive environment variables, auth tokens, or customer PII directly into LLM prompts.
− Strict API rate limits on enterprise Sentry organizations can throttle autonomous agents querying high-frequency incident bursts.
Side-by-side rival comparisons
Compare Sentry MCP Server vs GitHub MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 21,4 "method": "tools/call",5 "params": {6 "name": "get_issue",7 "arguments": {8 "issue_id": "109283401"9 }10 }11}
