Sentry MCP for Windsurf: Setup & Config

What you can do with Sentry in Windsurf

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.
• Request Seer analysis for an issue.

Before you start: Sentry in Windsurf

• 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 Windsurf configuration

1. Choose Windsurf configuration scope

   For Sentry MCP, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add Sentry MCP to Windsurf

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

3. Check Sentry MCP in Windsurf

   Sentry MCP: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "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 Windsurf

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

find_organizations

After refreshing Sentry in Windsurf settings, check Cascade's tool list for find_organizations.

Locate accessible organizations and their slugs.

find_projects

After refreshing Sentry in Windsurf settings, check Cascade's tool list for find_projects.

Find projects within a Sentry organization.

update_issue

After refreshing Sentry in Windsurf settings, check Cascade's tool list for update_issue.

search_events

After refreshing Sentry in Windsurf settings, check Cascade's tool list for search_events.

analyze_issue_with_seer

After refreshing Sentry in Windsurf settings, check Cascade's tool list for analyze_issue_with_seer.

Ask Seer to investigate an error and propose code fixes.

search_issues

After refreshing Sentry in Windsurf settings, check Cascade's tool list for search_issues.

get_sentry_resource

After refreshing Sentry in Windsurf settings, check Cascade's tool list for get_sentry_resource.

search_sentry_tools

After refreshing Sentry in Windsurf settings, check Cascade's tool list for search_sentry_tools.

Find additional operations in the Sentry MCP tool catalog.

execute_sentry_tool

After refreshing Sentry in Windsurf settings, check Cascade's tool list for execute_sentry_tool.

Run a discovered operation with arguments matching its schema.

Sentry: full stored tool descriptions

Troubleshooting Sentry in Windsurf

• Check npx @sentry/mcp-server (Node.js/npm) on the machine running Windsurf's MCP integration for Sentry MCP; refresh MCP and inspect Cascade's tools.
• Check EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, SENTRY_ACCESS_TOKEN for Sentry MCP; do not bypass a Windsurf permission error with a broad administrator token.
• Sentry MCP uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions