Sentry错误监控MCP服务

LLM Provider Configuration (required for AI-powered search tools)

EMBEDDED_AGENT_PROVIDER= # Required: 'openai' or 'anthropic' OPENAI_API_KEY= # Required if using OpenAI ANTHROPIC_API_KEY= # Required if using Anthropic

Test with local stdio mode (requires SENTRY_ACCESS_TOKEN)

pnpm -w run cli --access-token=TOKEN "query" ```

Note: The CLI defaults to http://localhost:5173. Override with --mcp-host or set MCP_URL environment variable.

Comprehensive testing playbooks: - Stdio testing: See docs/testing-stdio.md for complete guide on building, running, and testing the stdio implementation (IDEs, MCP Inspector) - Remote testing: See docs/testing-remote.md for complete guide on testing the remote server (OAuth, web UI, CLI client)

Getting Started

You'll find everything you need to know by visiting the deployed service in production:

<https://mcp.sentry.dev>

If you're looking to contribute, learn how it works, or to run this for self-hosted Sentry, continue below.

Optional overrides

SENTRY_HOST= # For self-hosted deployments MCP_DISABLE_SKILLS= # Disable specific skills (comma-separated, e.g. 'seer')

**Important:** Always set `EMBEDDED_AGENT_PROVIDER` to explicitly specify your LLM provider. Auto-detection based on API keys alone is deprecated and will be removed in a future release. See [docs/embedded-agents.md](docs/embedded-agents.md) for detailed configuration options.

#### Example MCP Configuration

If you leave the host variable unset, the CLI automatically targets the Sentry
SaaS service. Only set the override when you operate self-hosted Sentry.

For self-hosted instances that don't support Seer:

.env (in project root)

OPENAI_API_KEY= # Also required for AI-powered search tools in production

Note: The root `.env` file provides defaults for all packages. Individual packages can have their own `.env` files to override these defaults during development.

Once that's done you can run them using:

**Manual testing** (preferred for testing MCP changes):

Claude Code Plugin

Install as a Claude Code plugin for automatic subagent delegation:

claude plugin marketplace add getsentry/sentry-mcp
claude plugin install sentry-mcp@sentry-mcp

This provides a sentry-mcp subagent that Claude automatically delegates to when you ask about Sentry errors, issues, traces, or performance.

For forward-looking tool variants and features:

claude plugin install sentry-mcp@sentry-mcp-experimental

Stdio vs Remote

While this repository is focused on acting as an MCP service, we also support a stdio transport. This is still a work in progress, but is the easiest way to adapt run the MCP against a self-hosted Sentry install.

Note: The AI-powered search tools (search_events, search_issues, etc.) require an LLM provider (OpenAI or Anthropic). These tools use natural language processing to translate queries into Sentry's query syntax. Without a configured provider, these specific tools will be unavailable, but all other tools will function normally.

To utilize the stdio transport, you'll need to create an User Auth Token in Sentry with the necessary scopes. As of writing this is:

org:read
project:read
project:write
team:read
team:write
event:write

Launch the transport:

npx @sentry/mcp-server@latest --access-token=sentry-user-token

Need to connect to a self-hosted deployment? Add <code>--host</code> (hostname only, e.g. <code>--host=sentry.example.com</code>) when you run the command. For isolated internal deployments that only expose plain HTTP, also add <code>--insecure-http</code>.

Some features (like Seer) may not be available on self-hosted instances. You can disable specific skills to prevent unsupported tools from being exposed:

npx @sentry/mcp-server@latest --access-token=TOKEN --host=sentry.example.com --disable-skills=seer

For self-hosted instances without TLS:

npx @sentry/mcp-server@latest --access-token=TOKEN --host=sentry.internal:9000 --insecure-http

Environment Variables

```shell SENTRY_ACCESS_TOKEN= # Required: Your Sentry auth token