Sentry Issue Inspector
Retrieve and analyze error reports and debugging information from your Sentry.io account. Inspect issue details such as stacktraces, event counts, and timestamps to streamline your debugging workflow. Integrate seamlessly with tools like Claude Desktop and Zed for enhanced error monitoring.
Installation
Installing for Claude Desktop
Option 1: One-Command Installation
npx mcpbar@latest install anchor-g/mcp-sentry -c claudeThis command will automatically install and configure the Sentry Issue Inspector MCP server for your selected client.
Option 2: Manual Configuration
Run the command below to open your configuration file:
npx mcpbar@latest edit -c claudeAfter opening your configuration file, copy and paste this configuration:
View JSON configuration
{
"mcpServers": {
"Sentry Issue Inspector": {
"command": "uvx",
"args": [
"anchor-mcp-sentry"
],
"env": {
"YOUR_SENTRY_TOKEN": "${input:your_sentry_token}"
}
}
}
}mcp-server-sentry: A Sentry MCP server
Overview
A Model Context Protocol server for retrieving and analyzing issues from Sentry.io. This server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account.
Tools
get_sentry_issue- Retrieve and analyze a Sentry issue by ID or URL
- Input:
issue_id_or_url(string): Sentry issue ID or URL to analyze
- Returns: Issue details including:
- Title
- Issue ID
- Status
- Level
- First seen timestamp
- Last seen timestamp
- Event count
- Full stacktrace
Prompts
sentry-issue- Retrieve issue details from Sentry
- Input:
issue_id_or_url(string): Sentry issue ID or URL
- Returns: Formatted issue details as conversation context
Installation
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run mcp-server-sentry.
Using PIP
Alternatively you can install mcp-server-sentry via pip:
pip install mcp-server-sentry
After installation, you can run it as a script using:
python -m mcp_server_sentry
Configuration
Usage with Claude Desktop
Add this to your claude_desktop_config.json:
Using uvx
"mcpServers": {
"sentry": {
"command": "uvx",
"args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
}
Using docker
"mcpServers": {
"sentry": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
}
Using pip installation
"mcpServers": {
"sentry": {
"command": "python",
"args": ["-m", "mcp_server_sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
}
Usage with Zed
Add to your Zed settings.json:
Using uvx
"context_servers": [
"mcp-server-sentry": {
"command": {
"path": "uvx",
"args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
}
],
Using pip installation
"context_servers": {
"mcp-server-sentry": {
"command": "python",
"args": ["-m", "mcp_server_sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
},
Debugging
You can use the MCP inspector to debug the server. For uvx installations:
npx @modelcontextprotocol/inspector uvx mcp-server-sentry --auth-token YOUR_SENTRY_TOKEN
Or if you've installed the package in a specific directory or are developing on it:
cd path/to/servers/src/sentry
npx @modelcontextprotocol/inspector uv run mcp-server-sentry --auth-token YOUR_SENTRY_TOKEN
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Stars
0Forks
0Last commit
7 months agoRepository age
7 months
Auto-fetched from GitHub .
MCP servers similar to Sentry Issue Inspector:
Stars
Forks
Last commit
Stars
Forks
Last commit
Stars
Forks
Last commit