What it is
mcp-server-sentry is a Model Context Protocol server for retrieving and analyzing issues from Sentry.io. It provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account. It exposes one tool, get_sentry_issue, and one prompt, sentry-issue. The repository is in the archived servers collection.
Who it's for
- Developers who want to inspect Sentry issues and stacktraces from an MCP client
- Claude Desktop, VS Code or Zed users who want Sentry debugging context in their assistant
Requirements
Requirements
- A Sentry auth token (passed as
--auth-tokenor theSENTRY_AUTH_TOKENenvironment variable) uv/uvx, or pip with Python, or Docker, to run the server- An MCP client such as Claude Desktop, VS Code or Zed
Setup
Run with uvx (recommended)
With uv, no specific installation is needed.
uvxruns mcp-server-sentry directly. Add this to yourclaude_desktop_config.json.json"mcpServers": { "sentry": { "command": "uvx", "args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } }Install via pip
Alternatively, install the package with pip.
bashpip install mcp-server-sentryRun the pip-installed server
After installation, run it as a script.
bashpython -m mcp_server_sentryClaude Desktop config with Docker
Add this to your
claude_desktop_config.jsonto run the server via Docker.json"mcpServers": { "sentry": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } }Zed configuration with uvx
Add to your Zed settings.json.
json"context_servers": [ "mcp-server-sentry": { "command": { "path": "uvx", "args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } } ],
Examples
VS Code manual configuration (uvx)
json{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "auth_token",
"description": "Sentry Auth Token",
"password": true
}
],
"servers": {
"sentry": {
"command": "uvx",
"args": ["mcp-server-sentry"],
"env": {
"SENTRY_AUTH_TOKEN": "${input:auth_token}"
}
}
}
}
}What it does: Add to VS Code User Settings (JSON), or to .vscode/mcp.json in your workspace to share it. The mcp key is needed when using mcp.json. The token is prompted for as a password input.
Debug with the MCP inspector (uvx)
bashnpx @modelcontextprotocol/inspector uvx mcp-server-sentry --auth-token YOUR_SENTRY_TOKENWhat it does: Uses the MCP inspector to debug a uvx installation of the server.
Debug from a local checkout
bashcd path/to/servers/src/sentry
npx @modelcontextprotocol/inspector uv run mcp-server-sentry --auth-token YOUR_SENTRY_TOKENWhat it does: For a package installed in a specific directory or under development.
Using the get_sentry_issue tool
Promptget_sentry_issue with issue_id_or_url set to a Sentry issue ID or URLExpected output: The tool takes issue_id_or_url and returns the title, issue ID, status, level, first and last seen timestamps, event count and full stacktrace.
Pros & cons
Pros
- Pro:Returns detailed issue data including the full stacktrace, status, level, timestamps and event count
- Pro:Offers multiple run options: uvx, pip, and Docker
- Pro:Documented configuration for Claude Desktop, VS Code and Zed
- Pro:MIT licensed
Cons
- Con:Exposes only one tool, which retrieves a single issue by ID or URL
- Con:Lives in the servers-archived repository
- Con:Zed uvx example in the README appears to use array syntax with key-value entries, which may need correction
Images
