MCP Sentry Server (Node.js)

What is MCP Sentry Server (Node.js)?

MCP Sentry Server (Node.js) is a Node.js and TypeScript implementation of the Model Context Protocol (MCP) that integrates with the Sentry API to retrieve error reports and stacktraces through the MCP interface.

How to use MCP Sentry Server (Node.js)?

Install dependencies with pnpm install, build with pnpm build, then run with pnpm start or pnpm start:sse for SSE support. Configure a Sentry authentication token via a .env file or command-line arguments. For MCP client integration, add the provided JSON configuration to your MCP settings.

Key features of MCP Sentry Server (Node.js)

• Integration with Sentry API for error tracking and monitoring
• Support for both stdin/stdout and SSE transport
• Configurable SSE server port (default: 3579)
• Prompts: retrieve Sentry issue or find most triggered issue
• Tools: get Sentry issue or list of issues by URL
• Detailed issue data including title, status, severity, and stacktrace

Use cases of MCP Sentry Server (Node.js)

• Retrieve and analyze a specific Sentry issue by its ID or URL
• Find the Sentry issue affecting the most users from a list URL
• Integrate Sentry error data into AI-assisted debugging workflows

FAQ from MCP Sentry Server (Node.js)

What does MCP Sentry Server (Node.js) do?

It exposes Sentry error issue data (title, status, severity, stacktrace) as MCP prompts and tools, allowing LLMs or other MCP clients to fetch and analyze error reports.

What are the runtime requirements?

Node.js >= 20.0.0 and pnpm >= 10.5.2 are required.

How do I authenticate with Sentry?

Provide a Sentry authentication token via the SENTRY_TOKEN environment variable in a .env file, or pass it as a command-line argument with --auth-token.

Which transports are supported?

Standard MCP over stdin/stdout and SSE (Server-Sent Events) over HTTP on port 3579 (configurable).

How do I configure MCP Sentry Server (Node.js) in my MCP client?

Use the JSON configuration with the command and args set to npx -y @weekit/[email protected] and environment variables for the token and API base URL.