Sentry MCP Server
Allows interaction with the Sentry API to fetch issue and event details, list organization projects, and query project issues with filtering and pagination support.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sentry MCP Server show me the unresolved issues for my-api project from the last 7 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sentry MCP Server
@zereight/sentry-server
Sentry MCP(Model Context Protocol) Server. Allows interaction with the Sentry API to fetch issue and event details.
Related MCP server: Sentry
Usage
Using with Claude, Roo Code, Cline, etc.
Add the following configuration to your MCP settings file (e.g., mcp_settings.json):
{
"mcpServers": {
"sentry-server-npm": {
"command": "npx",
"args": [
"-y",
"@zereight/sentry-server"
],
"env": {
"SENTRY_AUTH_TOKEN": "YOUR_SENTRY_AUTH_TOKEN", // Required
"SENTRY_ORG_SLUG": "YOUR_ORG_SLUG", // Required: Your Sentry organization slug
"SENTRY_PROJECT_NAMES": "YOUR_PROJECT1,YOUR_PROJECT2", // Required: Comma-separated Sentry project slugs
"SENTRY_BASE_URL": "YOUR_SENTRY_BASE_URL" // Optional: Defaults to https://sentry.io
},
"disabled": false
}
}
}Replace placeholder values like "YOUR_SENTRY_AUTH_TOKEN", "YOUR_ORG_SLUG", and "YOUR_PROJECT1,YOUR_PROJECT2" with your actual Sentry details. Provide project slugs separated by commas. Project slugs are used in Sentry URLs (e.g., https://<org-slug>.sentry.io/settings/projects/<project-slug>/). Auth tokens can be generated in User Settings > Auth Tokens.
Using with Cursor (or direct CLI)
When using with Cursor or running directly, you can set up environment variables and run the server as follows:
env SENTRY_AUTH_TOKEN=YOUR_SENTRY_AUTH_TOKEN \
SENTRY_ORG_SLUG=YOUR_ORG_SLUG \
SENTRY_PROJECT_NAMES=YOUR_PROJECT1,YOUR_PROJECT2 \
SENTRY_BASE_URL=YOUR_SENTRY_BASE_URL \
npx @zereight/sentry-serverSENTRY_AUTH_TOKEN(Required): Your Sentry authentication token.SENTRY_ORG_SLUG(Required): The slug of your Sentry organization.SENTRY_PROJECT_NAMES(Required): Comma-separated names (slugs) of your Sentry projects.SENTRY_BASE_URL(Optional): The base URL for your Sentry instance (e.g., for self-hosted). Defaults tohttps://sentry.io.
Tools ๐ ๏ธ
get_sentry_issueFetches details for a specific Sentry issue. โน๏ธ
Inputs:
issue_id_or_url(string, required): The Sentry issue ID or the full URL of the issue page.
Returns: Detailed information about the issue (JSON string).
list_organization_projectsLists all projects for the configured Sentry organization. ๐
Inputs: None
Returns: A list of project objects (JSON string).
list_project_issuesLists issues for a specific project, with optional filtering. ๐
Inputs:
organization_slug(string, optional): The slug of the organization. Defaults toSENTRY_ORG_SLUGenv var.project_slug(string, required): The slug of the project to list issues for.query(string, optional): Sentry search query to filter issues (e.g., "is:unresolved", "assignee:me").statsPeriod(string, optional): Time period for statistics (e.g., "24h", "14d", "auto").cursor(string, optional): Pagination cursor for fetching next/previous page.
Returns: A list of issue objects and pagination information (JSON string).
get_event_detailsGets details for a specific event within a project. ๐
Inputs:
organization_slug(string, optional): The slug of the organization. Defaults toSENTRY_ORG_SLUGenv var.project_slug(string, required): The slug of the project the event belongs to.event_id(string, required): The ID of the event to retrieve.
Returns: Detailed information about the specific event (JSON string).
Environment Variable Configuration
Before running the server, you must set the following environment variables:
SENTRY_AUTH_TOKEN=YOUR_SENTRY_AUTH_TOKEN
SENTRY_ORG_SLUG=YOUR_ORG_SLUG
SENTRY_PROJECT_NAMES=YOUR_PROJECT_NAME1,YOUR_PROJECT_NAME2Optionally, you can also set:
SENTRY_BASE_URL=YOUR_SENTRY_BASE_URL # Default: https://sentry.ioThe Inspector will provide a URL to access debugging tools in your browser.
License
MIT License
Available Tools
4 toolsget_event_detailsC
Get details for a specific event within a project.
Inputs: project_slug (required), event_id (required), organization_slug.
get_sentry_issueC
Get details for a specific Sentry issue using its ID or URL
Inputs: issue_id_or_url (required).
list_organization_projectsB
List all projects for the configured Sentry organization
Inputs: no named parameters.
list_project_issuesC
List issues for a specific project, with optional filtering.
Inputs: project_slug (required), organization_slug, query, statsPeriod, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 4 tools
The tools have mostly distinct purposes: get_event_details and get_sentry_issue both retrieve details but target different resources (events vs. issues), while list_organization_projects and list_project_issues handle listing operations for different scopes. There is minor potential confusion between the two 'get' tools since both fetch details, but their descriptions clarify the resource distinction.
All tool names follow a consistent verb_noun pattern (e.g., get_event_details, list_organization_projects) with clear, descriptive naming. There are no deviations in style or convention across the set.
With only 4 tools, the server feels somewhat thin for a Sentry integration, which typically involves more operations like creating issues, updating statuses, or managing alerts. While the tools cover basic read and list functions, the count is borderline low for the domain's scope.
The toolset is significantly incomplete for a Sentry server, lacking essential operations such as creating or updating issues, resolving events, or managing project settings. It only supports read and list functions, leaving major gaps in CRUD coverage that will hinder agent workflows.
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Let AI agents list, read and resolve Bugsly error-tracking issues and check monitors.
1MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Investigate errors, track deployments, analyze performance, and manage application monitoring
Related MCP Servers
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with Sentry for error tracking and monitoring, allowing retrieval and analysis of error data, project management, and performance monitoring through the Sentry API.1121ISC
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to retrieve and analyze Sentry issues, including error reports, stacktraces, and debugging information from Sentry.io.10 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Sentry organizations, projects, and issues directly from MCP clients like Claude Code.18 npmMIT