CookiesForAI

Sentry MCP server

The Sentry MCP server gives AI coding agents access to your Sentry account: search errors and events, read issue details and stack traces, look at performance data and triage issues while fixing code.

By Sentry Official · Updated

Connect Sentry

Claude Code, scoped to one project

Terminal
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}

Claude Code, as a plugin with a Sentry subagent

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

Cursor and other clients with a JSON config

Config
{"mcpServers": {"sentry": {"url": "https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}"}}}

Local server, for example against self-hosted Sentry

Terminal
npx @sentry/mcp-server@latest --access-token=sentry-user-token --host=sentry.example.com

The first connection to the hosted server opens a Sentry OAuth sign-in. In VS Code, run MCP: Add Server, choose HTTP and paste the endpoint. Add ?experimental=1 to the URL for newer tool variants.

What the Sentry MCP server does

The Sentry MCP server connects an AI coding agent to Sentry, the error and performance monitoring service. Sentry built it for developers who debug with an agent at their side: the agent can look up the issues in a project, read an error's stack trace and events, search events and traces, check performance problems and read Sentry's own documentation. Project management tools let it assign or resolve issues and manage projects, and a Seer group hands an issue to Sentry's AI root-cause analysis.

Sentry's search tools accept plain-language questions, such as "errors in checkout in the last day", and translate them into Sentry's query syntax with a language model. On the hosted server Sentry handles that; on a self-run server you must configure an OpenAI, Azure OpenAI, Anthropic or OpenRouter key for those tools to work. Tools are grouped into skills that you can narrow with a URL parameter, and scoping the URL to one organization or project hides discovery tools the agent does not need.

Sentry hosts the server at mcp.sentry.dev with OAuth sign-in. The code also runs locally with npx, which is the way to connect a self-hosted Sentry. The source repo was renamed from sentry-mcp to getsentry/toolkit and had 875 GitHub stars on 2026-10-01; it uses the Functional Source License, which converts to Apache-2.0 after two years.

Tools it gives your agent

  • search_issues
  • search_events
  • get_issue_details
  • get_event_stacktrace
  • get_trace_details
  • update_issue
  • add_issue_note
  • analyze_issue_with_seer
  • find_projects
  • find_releases
  • search_docs
  • create_project

When to use Sentry

  • You want the agent to read a production error's stack trace and fix the code that caused it.
  • You want a list of the newest or most frequent issues in a project before a release.
  • You want to resolve or assign Sentry issues without leaving your editor.
  • You run self-hosted Sentry and want the same tools against your own instance.

When to pick something else

  • General Sentry administration: Sentry says it focuses the tools on debugging workflows, not on covering the whole Sentry API.
  • Self-run setups without an LLM key: the plain-language search tools need an OpenAI, Anthropic or OpenRouter key when you run the server yourself.

What Sentry needs

  • A Sentry account (OAuth) or a Sentry user auth token for the local server

What the Sentry MCP server costs

No extra charge: Sentry lists MCP access on its free Developer plan; paid plans add volume and users, and Seer, Sentry's AI debugger, costs extra.

Current prices: sentry.io . We do not list prices: vendors change them often, so check the publisher's own page.

Questions people ask

Is the Sentry MCP server free?

Using it costs nothing extra: Sentry lists MCP access on its free Developer plan. You pay only for your Sentry plan and for Seer if you use its AI analysis (pricing page, 2026-10-01).

Can the Sentry MCP server change anything, or only read?

It can change things: it can update issues, for example to assign or resolve them, and manage projects. Use the skills parameter to expose only the read and inspect tools.

  • AWS: The AWS MCP servers give AI agents access to AWS: a managed AWS MCP Server for API calls and docs, plus more than 50 open-source servers for services like CDK, EKS, Lambda and DynamoDB.
  • Cloudflare: The Cloudflare MCP servers give AI agents access to a Cloudflare account through hosted endpoints: read Workers logs and builds, manage bindings, check DNS analytics, search the docs and render web pages.
  • Kubernetes: The Kubernetes MCP server gives AI agents direct access to Kubernetes and OpenShift clusters: list and edit any resource, read pod logs, exec into pods, view events and install Helm charts.
  • Terraform: The Terraform MCP server gives AI agents current Terraform Registry data on providers, modules and policies, and with a token manages HCP Terraform and Terraform Enterprise workspaces, runs and plans.