Share:
About
Complements the base Sentry integration with richer issue search: filter by project, environment, release, or tag, and pull full event payloads for the assistant to reason over. Useful when triaging noisy alerts across multiple projects.
Example tools
Illustrative tool names — the actual tool set is defined by the server at runtime.
list_resources
Enumerate resources exposed by this MCP
get_resource
Fetch a resource by ID
invoke
Invoke the primary action of this MCP
Screenshots
No screenshots yet.
Frequently Asked Questions
Common questions about Sentry Issues MCP.
- What is the Sentry Issues MCP used for?
- The Sentry Issues MCP enhances issue search within Sentry, allowing filtering by project, environment, release, or tag. It also retrieves full event payloads, aiding in the triage of alerts across multiple projects.
- How do I configure Sentry Issues MCP in an MCP client?
- Configuration typically involves providing an API key for authentication. Specific steps depend on the MCP client, but generally, you will add the MCP and input your Sentry API key when prompted.
- Does the Sentry Issues MCP require an API key?
- Yes, the Sentry Issues MCP uses an API key for authentication. You will need to provide a valid Sentry API key to use its features.
- What capabilities does the Sentry Issues MCP offer?
- The Sentry Issues MCP allows detailed searches for Sentry issues using various filters and provides access to complete event details. This enables assistants to process and reason over Sentry event data.
- What is the cost associated with using the Sentry Issues MCP?
- The Sentry Issues MCP itself is a protocol integration. The cost depends on your existing Sentry plan and any associated usage fees for the Sentry service.
- What is a prerequisite for using the Sentry Issues MCP?
- A key prerequisite for using the Sentry Issues MCP is an active Sentry account with appropriate permissions to generate API keys and access issue data.
Install Sentry Issues MCP
Claude Desktop
Add this to claude_desktop_config.json.
{
"mcpServers": {
"sentry-issues": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sentry-issues"
]
}
}
}Cursor
Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"sentry-issues": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sentry-issues"
]
}
}
}VS Code
Add this to your workspace settings.json.
{
"mcp.servers": {
"sentry-issues": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sentry-issues"
]
}
}
}Reviews
Sign in to leave a review.
No reviews yet. Be the first!
Discussion(0)
No comments yet.