mcp

Start a local Sentry MCP server

Usage

sentry mcp [<org/project>]

Start a local Sentry MCP server

Arguments:

Argument	Description
[<org/project>]	<org>/ (an organization) or <org>/<project> to limit calls to

Options:

Option	Description
--access-token <access-token>	Deprecated: set SENTRY_AUTH_TOKEN instead
--org <org>	Limit every call to this organization
--project <project>	Limit calls to this project
--skills <skills>	Skills to grant, comma-separated (default: active skills; seer is left out on self-hosted)
--all-skills	Grant every active skill, including seer on self-hosted
--disable-skills <disable-skills>	Skills to remove, comma-separated
--experimental	Enable forward-looking tool variants and experimental features
--agent-provider <agent-provider>	LLM provider for AI-powered search: openai, azure-openai, anthropic, or openrouter
--openai-base-url <openai-base-url>	OpenAI API base URL
--openai-model <openai-model>	OpenAI model (default: gpt-5)
--anthropic-base-url <anthropic-base-url>	Anthropic API base URL
--anthropic-model <anthropic-model>	Anthropic model (default: claude-sonnet-4-5)
--mcp-url <mcp-url>	MCP server URL reported in telemetry

Examples:

# Start the server with the current CLI login
sentry mcp

# Limit every call to one organization
sentry mcp acme/

# Limit calls to one project
sentry mcp acme/web

# Grant every skill, including seer on self-hosted
sentry mcp --all-skills

# Grant only some skills
sentry mcp --skills inspect,triage

# Pick the LLM provider for AI-powered search
sentry mcp --agent-provider anthropic

All commands support --json for machine-readable output and --fields to select specific JSON fields.

sentry mcp starts the local stdio Sentry MCP server using the active Sentry CLI session. Authenticate once with sentry auth login; no separate MCP login or token cache is required.

Configure an MCP client

Point your MCP client at the installed Sentry CLI:

{
  "mcpServers": {
    "sentry": {
      "command": "sentry",
      "args": ["mcp"]
    }
  }
}

For a self-hosted instance, first authenticate the CLI against that host. You can also pick the instance for this MCP server with SENTRY_HOST or SENTRY_URL (an http:// URL for plain HTTP), the same as for other commands:

{
  "mcpServers": {
    "sentry": {
      "command": "sentry",
      "args": ["mcp"],
      "env": {
        "SENTRY_HOST": "sentry.example.com"
      }
    }
  }
}

--host, --url, and --insecure-http still work but are deprecated.

Limit the server to an organization or project

Pass <org>/ to limit every call to one organization, or <org>/<project> to one project:

{
  "mcpServers": {
    "sentry": {
      "command": "sentry",
      "args": ["mcp", "acme/web"]
    }
  }
}

--org and --project do the same; a target and a flag that name different values are an error. A bare acme is refused, because other commands read it as a project search: pass acme/ for the organization. The target takes no URL; pick the Sentry instance with SENTRY_HOST or SENTRY_URL.