Sentry MCP Server

What is Sentry MCP Server?

Sentry MCP Server integrates Sentry error tracking into your development workflow by providing access to release health data and issue details through the Model Context Protocol (MCP). It is designed for developers using MCP-enabled environments like VS Code with the Cline extension.

How to use Sentry MCP Server?

Clone the repository, install dependencies (npm install), build (npm run build), then add the server to your MCP client’s configuration with an absolute path to the built index.js. Create a .env file in the project root with your Sentry credentials (SENTRY_AUTH_TOKEN, SENTRY_BASE_URL, SENTRY_ORG_SLUG). Restart your MCP client to load the server.

Key features of Sentry MCP Server

• List recent releases with new issue counts.
• View release health statistics (crash-free rates, sessions).
• Fetch detailed information about specific Sentry issues.
• Retrieve all issues associated with a given release.
• Works with both Sentry.io cloud and self-hosted Sentry.
• Inspect server configuration and connection status.

Use cases of Sentry MCP Server

• Monitor release health without leaving your code editor.
• Investigate issue details directly from your MCP client.
• Track new issues introduced per release version.
• Quickly check crash-free rates for a specific release.
• Verify server setup with the inspect tool.

FAQ from Sentry MCP Server

What data can I access with this server?

You can access release lists, release health statistics (crash-free rates, session counts), issue details, and issues per release. All data comes from the Sentry API.

Can I use a self-hosted Sentry instance?

Yes. Set SENTRY_BASE_URL to your instance’s API endpoint (e.g., https://your-sentry-instance.com/api/0/). The server supports both cloud and self-hosted environments.

What environment variables are required?

Three variables: SENTRY_AUTH_TOKEN (API token from Sentry), SENTRY_BASE_URL (API endpoint), and SENTRY_ORG_SLUG (your organization slug). These are typically set in a .env file in the project root.

How do I verify the server is working?

Use the inspect_sentry tool (no arguments needed). It returns configuration details, available capabilities, and environment info to confirm the connection to Sentry is successful.

What transport does this server use?

The server communicates via MCP over stdio, as configured in the MCP client settings (command node with the path to build/index.js).