This MCP server exposes a set of tools that let you interact with Sentry data directly from your MCP client (for example, within VS Code using Cline). You can inspect the server configuration and connection to Sentry, list the most recent releases for a project, fetch all releases for a project, view health statistics for a specific release, retrieve details about a specific Sentry issue, and list all issues associated with a given release. The tools are designed to work with both Sentry cloud (sentry.io) and self-hosted instances by using standard Sentry API endpoints configured via environment variables. Start by running the server so it can authenticate with your Sentry account, then configure your MCP client to point to the built index.js file using an absolute path in your settings file. Use the inspect_sentry tool to verify connectivity and available capabilities, then call the other tools with the required arguments (project_slug, org_slug, release_version, issue_id, etc.).

Prerequisites:

• Node.js (LTS recommended) and npm installed on your machine
• Git to clone the repository
• Access to a Sentry account with an API token and the appropriate permissions

Installation steps:

1. Clone the repository git clone https://github.com/srcgrp/sentry-mcp-server.git cd sentry-mcp-server

2. Install dependencies and build npm install npm run build

   This generates the executable server script in the build/ directory

3. Run the server (example) node build/index.js

   Or use your process manager to keep it running in the background

4. Configure MCP client Add the server to your MCP client's configuration (e.g., cline_mcp_settings.json) with the absolute path to the built index.js, and set environment variables as needed. Example snippet: { "mcpServers": { "sentry-local": { "command": "node", "args": ["/absolute/path/to/sentry-mcp-server/build/index.js"], "env": { "SENTRY_AUTH_TOKEN": "YOUR_SENTRY_AUTH_TOKEN", "SENTRY_BASE_URL": "YOUR_SENTRY_API_ENDPOINT", "SENTRY_ORG_SLUG": "your-organization-slug" }, "disabled": false, "autoApprove": [] } } }

5. Restart your MCP client after updating settings.

Environment variables are required for Sentry access. Ensure SENTRY_BASE_URL matches your Sentry instance API endpoint (cloud users typically use https://sentry.io/api/0/). If you switch between Sentry cloud and a self-hosted instance, update SENTRY_BASE_URL accordingly. The inspect_sentry tool is useful for validating connectivity before making API calls. When sharing configuration files, prefer using absolute paths to the built index.js to avoid path resolution issues. If you encounter authentication errors, double-check that your SENTRY_AUTH_TOKEN has the necessary scopes for project and issue data access.