Sentry's MCP Server

Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.

The Sentry MCP Server provides a secure way of bringing Sentry's full issue context into systems that are able to leverage the Model Context Protocol (MCP). Sentry hosts and manages a remote MCP server, which you can connect to and leverage centrally. With the MCP, you 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

Sentry MCP Server Query in Claude

Most clients that natively support MCP can be configured using a mcp_config.json file or an equivalent. In these systems, adding the server configuration to the file will setup an MCP server:

Copied
{
  "mcpServers": {
    "Sentry": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.sentry.dev/sse"]
    }
  }
}

This setup uses the Remote-MCP server configuration, enabling most clients to connect to the Sentry MCP, authenticate via OAuth, and access the available tools.

Alternatively, if you don't want the Remote-MCP server, 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.

Available Sentry MCP Tools

  • 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.

Sentry MCP using Autofix

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 and editing the mcp.json file

By adding the server in CMD+Shift+P and selecting MCP: Add Server

Was this helpful?
Help improve this content
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").