Sentry MCP Server
A Model Context Protocol (MCP) server that provides a secure way of connecting IDE's and LLMs access to Sentry to retrieve context for debugging and analysis.
The Sentry MCP Server is currently in beta. Beta features are still in progress and may have bugs. Please reach out on GitHub if you have any feedback or concerns.
The Sentry MCP Server provides a secure way of bringing Sentry context into systems that are able to leverage the Model Context Protocol (MCP). Sentry offers a remote MCP server that is hosted and managed by Sentry, and designed for developers to connect to and leverage centrally. With the MCP, developers can:
- Access Sentry issues and errors
- Search for errors in specific files
- Query projects and organizations
- List and create Sentry DSN's for projects
- Execute autofix runs and retrieve autofix status and details
Most clients that natively support MCP support configuration via a mcp_config.json
file or an equivalent. In these systems, adding the server configuration to the file will setup an MCP server
{
"mcpServers": {
"Sentry": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.sentry.dev/sse"]
}
}
}
This configuration uses the Remote-MCP server configuration and allows most clients to connect to the Sentry MCP, authenticating via OAuth, and expose the available tools.
Alternatively, if the Remote-MCP server is not desired, you can run the MCP Server locally in STDIO mode by following the instructions in the README.
Once configured via one of these methods, you'll be able to view the available tools within your client and use them as part of your LLM calls.
- Tell me about the issues in my
project
- Check Sentry for errors in
file.tsx
and propose solutions. - Diagnose issue
issue id
and propose solutions. - Create a new project in Sentry for
service-name
and setup local instrumentation using it. - Use Sentry's autofix feature, and help me analyze and propose a solution for
issue id
.
The Sentry MCP Server has been verified to work in
By accessing the developer tools via CMD + ,
-> Developer
-> Edit Config
-> edit the claude_desktop_config.json
file
Via the Configure MCP
option in Cascade (CMD + L)
Via the Cursor
-> Settings
-> Cursor Settings
-> MCP path
and editing the mcp.json
file
By adding the server in CMD+Shift+P
and selecting MCP: Add Server
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").