1. Home
  2. Sentry MCP
  3. Sentry MCP for Claude Desktop: Setup & Config

Data as of

Sentry MCP for Claude Desktop: Setup & Config

Claude Desktop: Sentry MCP brings production issues, events, and traces into coding-assistant workflows.

What you can do with Sentry in Claude Desktop

Bring Sentry investigation and issue triage directly into a human-guided coding session.

  • Investigate production errors alongside application code.
  • Find organizations and project identifiers for follow-up requests.
  • Resolve, reopen, ignore, or assign issues.

Before you start: Sentry in Claude Desktop

  • Node.js with npx
  • Sentry user token
  • LLM provider credentials for AI-powered search

This is the README stdio configuration. Required token scopes are event:write, project:write, team:read, org:read, team:write, and project:read. Remote access is also documented at https://mcp.sentry.dev/mcp. Use --host for self-hosted Sentry; unsupported skills can be disabled.

Sentry Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Sentry MCP, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Sentry MCP to Claude Desktop

    Use the sentry-mcp entry below in mcpServers. Keep Sentry MCP's documented stdio connection fields and your other Claude Desktop entries.

  3. Check Sentry MCP in Claude Desktop

    Sentry MCP: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "sentry-mcp": {
      "command": "npx",
      "args": [
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_ACCESS_TOKEN": "<Sentry user auth token with documented scopes>",
        "EMBEDDED_AGENT_PROVIDER": "<Explicit LLM provider for AI-powered search>",
        "OPENAI_API_KEY": "<OpenAI key if selecting OpenAI>"
      }
    }
  }
}

Sentry tools available to Claude Desktop

Sentry's stored tool list documents 9 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

find_organizations

When Claude Desktop requests find_organizations from Sentry, review the action before approving it.

Locate accessible organizations and their slugs.

find_projects

When Claude Desktop requests find_projects from Sentry, review the action before approving it.

Find projects within a Sentry organization.

update_issue

When Claude Desktop requests update_issue from Sentry, review the action before approving it.

Change an issue status or assignment.

search_events

When Claude Desktop requests search_events from Sentry, review the action before approving it.

Search events and replays, including statistical queries.

analyze_issue_with_seer

When Claude Desktop requests analyze_issue_with_seer from Sentry, review the action before approving it.

Ask Seer to investigate an error and propose code fixes.

search_issues

When Claude Desktop requests search_issues from Sentry, review the action before approving it.

get_sentry_resource

When Claude Desktop requests get_sentry_resource from Sentry, review the action before approving it.

search_sentry_tools

When Claude Desktop requests search_sentry_tools from Sentry, review the action before approving it.

execute_sentry_tool

When Claude Desktop requests execute_sentry_tool from Sentry, review the action before approving it.

Sentry: full stored tool descriptions

Troubleshooting Sentry in Claude Desktop

  • Fully quit and reopen Claude Desktop for Sentry MCP. If npx @sentry/mcp-server (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's Sentry MCP entry, check EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, SENTRY_ACCESS_TOKEN. Keep secrets out of shared screenshots and repositories.
  • Sentry MCP uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: AI-powered search needs an LLM provider.
  • Known limitation: Some self-hosted deployments lack Seer.
  • Known limitation: The README describes stdio support as work in progress.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Sentry MCP — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Sentry MCP from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's sentry-mcp example uses stdio.

Sentry MCP's Claude Desktop configuration invokes npx @sentry/mcp-server (Node.js/npm).

Claude Desktop's Sentry MCP example references EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, SENTRY_ACCESS_TOKEN. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Sentry MCP's stored list contains 9 tools, including find_organizations, find_projects, update_issue. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

No. The README prioritizes developer debugging and human-guided coding agents.

Non-AI tools remain available, but AI-powered search tools require a configured provider.

Yes. The stdio launch supports a hostname override, with optional plain HTTP for isolated internal deployments.