Sentry MCP Server (remote)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "sentry-mcp-server-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.sentry.dev/mcp"
      ]
    }
  }
}

Before you start

• A Sentry account (SaaS or self-hosted) with access to the org/projects you want to query
• For the hosted server: an MCP client that supports remote MCP over HTTP with OAuth (the OAuth flow runs in your browser)
• For the local stdio variant: Node.js plus a Sentry User Auth Token with scopes such as org:read, project:read/write, team:read/write, and event:write
• Seer must be enabled on your Sentry org to use the AI root-cause analysis tool

About Sentry MCP Server (remote)

Tools & capabilities (12)

When to use it

• Use it when an exception shows up in Sentry and you want the assistant to pull the stack trace and surrounding context into your editor
• Use it when you want plain-English queries over errors and events instead of writing Sentry search syntax by hand
• Use it when you need AI root-cause analysis on a tricky issue via Sentry's Seer
• Use it when correlating a slow request with its distributed trace and spans
• Use it when triaging: listing recent issues for a project and updating their status or assignee from chat

Quick setup

1. 1Add the remote server URL `https://mcp.sentry.dev/mcp` to your MCP client (or install via the client's connector UI)
2. 2Complete the OAuth flow in your browser to grant access to your Sentry org
3. 3Approve the requested scopes for the projects you want the assistant to read
4. 4Restart or reconnect your MCP client so the Sentry tools load
5. 5Verify by asking the assistant to list your organizations or recent issues
6. 6Alternatively, run `npx @sentry/mcp-server@latest --access-token=...` locally for stdio mode

Sentry MCP Server (remote) FAQ