Sentry Official Featured

Frequently asked questions

What does the Sentry MCP server do?

Sentry Toolkit This repository contains the Sentry CLI, the Sentry MCP server, and shared packages. For the CLI, see the CLI guide and the published documentation at ://cli.sentry.dev/>. The documentation index covers both products and shared contributor guidance. Sentry MCP Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality. This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools. It's based on Cloudflare's work towards remote MCPs. Getting Started You'll find everything you need to know by visiting the deployed service in production: ://mcp.sentry.dev> If you're looking to contribute, learn how it works, or to run this for self-hosted Sentry, continue below. Claude Code Plugin Install as a Claude Code plugin for automatic subagent delegation: 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: 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 errors , search traces , search logs , search issues , etc.) require an LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter). 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: Launch the transport: Need to connect to a self-hosted deployment? Add >--host > (hostname only, e.g. >--host=sentry.example.com >) when you run the command. For isolated internal deployments that only expose plain HTTP, also add >--insecure-http >. Seer is not part of self-hosted Sentry, so the seer skill is left out of the default skill set whenever --host points at a non- sentry.io host. If your self-hosted deployment does run Seer, opt back in explicitly: You can also disable any other skill to prevent unsupported tools from being exposed: For self-hosted instances without TLS: Remote with an Explicit Sentry Token Remote clients that support custom HTTP headers can pass an upstream Sentry API token directly to the Cloudflare transport: Sentry-Bearer is intentionally separate from Bearer : Bearer is reserved for MCP OAuth access tokens. With Sentry-Bearer , the worker does not store, validate, exchange, or refresh the upstream token. It forwards the token through the same Sentry API calls used by OAuth-backed sessions, and the client or upstream provider remains responsible for token lifetime and refresh. Direct remote auth defaults to all active MCP skills. You can narrow the exposed tools with ?skills=inspect,triage or ?disable-skills=seer . Environment Variables 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/operations/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. Setting SENTRY HOST to a self-hosted host also drops the seer skill from the default set, since Seer is not available on self-hosted Sentry. For a self-hosted deployment that does run Seer, opt in with MCP SKILLS : MCP Inspector MCP includes an Inspector, to easily test the service: Enter the MCP server URL ( ://localhost:5173>) and hit connect. This should trigger the authentication flow for you. Note: If you have issues with your OAuth flow when accessing the inspector on 127.0.0.1 , try using localhost instead by visiting Local Development To contribute changes, you'll need to set up your local environment: Set up environment and agent skills: This also runs npx @sentry/dotagents install to install shared skills from getsentry/skills into .agents/skills/ (symlinked into .claude/skills and .cursor/skills ). If you need to update skills later, run it directly: Create an OAuth App in Sentry (Settings => API => Applications): Homepage URL: Authorized Redirect URIs: Note your Client ID and generate a Client secret Configure your credentials: Edit .env in the root directory and add either OPENAI API KEY or OPENROUTER API KEY Edit packages/mcp-cloudflare/.env and add: SENTRY CLIENT ID=your development sentry client id SENTRY CLIENT SECRET=your development sentry client secret COOKIE SECRET=my-super-secret-cookie Start the development server: Verify Run the server locally to make it available at To test the local server, enter into Inspector and hit connect. Once you follow the prompts, you'll be able to "List Tools". Tests There are three test suites included: unit tests, evaluations, and manual testing. Unit tests can be run using: Evaluations require a .env file in the project root with some config: 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): Note: The CLI defaults to 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) Development Notes Automated Code Review This repository uses automated code review tools (like Cursor BugBot) to help identify potential issues in pull requests. These tools provide helpful feedback and suggestions, but we do not recommend making these checks required as the accuracy is still evolving and can produce false positives. The automated reviews should be treated as: ✅ Helpful suggestions to consider during code review ✅ Starting points for discussion and improvement ❌ Not blocking requirements for merging PRs ❌ Not replacements for human code review When addressing automated feedback, focus on the underlying concerns rather than strictly following every suggestion. Contributor Documentation Looking to contribute? Start at the Toolkit documentation index for CLI, MCP, and shared guides. See AGENTS.md for repository rules and packages/cli/AGENTS.md for CLI-specific rules.

How do I install Sentry?

Run the install command shown above, then paste the config for your client (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) into its MCP settings and restart the client.

Is Sentry free to use?

The MCP server itself is free to install. The source is public on https://github.com/getsentry/sentry-mcp. Any third-party service it calls may require its own API key and account.

Which clients support Sentry?

Any MCP-compatible client can use it, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and custom agents.