1. Home
  2. Sentry MCP
  3. Sentry MCP for VS Code: Setup & Config

Data as of

Sentry MCP for VS Code: Setup & Config

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

Sentry MCP VS Code configuration

  1. Choose VS Code configuration scope

    For Sentry MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Sentry MCP to VS Code

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

  3. Check Sentry MCP in VS Code

    Sentry MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "sentry-mcp": {
      "type": "stdio",
      "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 in VS Code: stdio checks

  • Make npx @sentry/mcp-server (Node.js/npm) available in the workspace, container, or remote environment hosting Sentry MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For Sentry MCP, keep EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, SENTRY_ACCESS_TOKEN out of version control; VS Code documents input variables and secret handling.
  • Sentry MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
find_organizations, find_projects, update_issue

Sentry MCP — details. VS Code guide

Frequently asked questions

For Sentry MCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's sentry-mcp example uses stdio.

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

VS Code'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 VS Code's connected tool list; the stored list is not a live check.