Sentry MCP Server 🔍

What is Sentry MCP Server 🔍?

A TypeScript implementation of a Sentry MCP (Modern Context Protocol) tool that enables AI agents to access and analyze Sentry error data by retrieving issues, viewing stacktraces, and reading formatted metadata.

How to use Sentry MCP Server 🔍?

Install with pnpm install, configure a .env file with your Sentry auth token (and optionally a custom API base URL), then run pnpm build && pnpm start. The server exposes a tool interface (get_sentry_issue) and a prompt interface (sentry-issue), both accepting an issue ID or URL.

Key features of Sentry MCP Server 🔍

• Retrieve and analyze Sentry issues via AI agents
• Get formatted issue details and metadata
• View detailed stacktraces
• Support for both tool and prompt interfaces
• Robust error handling and real-time communication

Use cases of Sentry MCP Server 🔍

• Debugging crashes by querying Sentry issues from an AI assistant
• Integrating error analysis into Cursor IDE for a seamless development workflow
• Automating bug report enrichment with stacktrace and metadata
• Building AI‑powered diagnostic tools that consume Sentry data

FAQ from Sentry MCP Server 🔍

What does it require to run?

Node.js, pnpm, and a valid Sentry authentication token (configured via the SENTRY_AUTH_TOKEN environment variable). The server runs on port 1337 by default.

How does it connect to Sentry?

It uses the Sentry API (default base URL https://sentry.io/api/0/). The optional SENTRY_API_BASE variable lets you point to a different Sentry instance.

Does it support both tools and prompts?

Yes. The MCP interface provides a get_sentry_issue tool and a sentry-issue prompt, both accepting the same issue_id_or_url parameter.

Can I use it with Cursor IDE?

Yes. Start the server locally, then configure Cursor to use the local MCP server for in‑IDE Sentry issue analysis.

What transports or authentication does the server use?

The README mentions MCP (Modern Context Protocol) with tool and prompt interfaces. Authentication is done via the Sentry auth token supplied in the .env file. No other transports (e.g., HTTP, stdio) are specified.