MCP server · Developer tools

OfficialSource ValidatedRead-writeFSL-1.1-ALv2Updated August 2026

Sentry MCP

Inspect errors, traces and issues, then perform scoped issue triage through Sentry's official MCP service.

Quick verdict

A high-value production-debugging profile with a credible least-privilege story, provided the directory preserves the narrowed skill set and labels the license honestly as source-available rather than open source.

  • MaintainerSentry (official)
  • Security scopeRead-write
  • Transportsstreamable-http, stdio
  • Install channelremote · https://mcp.sentry.dev/mcp?skills=inspect,triage
  • EvidenceSource Validated
  • LicenseFSL-1.1-ALv2 · Source-available

Sentry MCP is first-party middleware for coding assistants that investigate production errors, traces, issues and Sentry documentation. Its skill-based authorization can add issue triage, Seer analysis and project management. This profile narrows the hosted OAuth connection to the inspect and triage skills, retaining reversible issue updates while excluding Seer and project-management create/modify tools from the advertised surface.

MCP security best practices

Install Sentry MCP

http https://mcp.sentry.dev/mcp

Config entry (mcpServers)
{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp?skills=inspect,triage"
    }
  }
}

Sentry-hosted endpoint, narrowed by the ?skills=inspect,triage query to read/investigate and reversible-triage tools only; the service's default skill set is broader (adds Seer analysis and project-management create/modify tools) and this profile deliberately does not enable it. Hosted use defaults to Sentry OAuth; clients with custom-header support can instead send a Sentry API token as Authorization: Sentry-Bearer <token>. The same-family @sentry/mcp-server stdio package is a self-hosted/local path for self-hosted Sentry, documented as a work in progress.

Credentials

No static secret goes in this config, but this server still requires account authorization. Connecting it starts an interactive sign-in and consent flow against the account it reaches, and whatever that account is allowed to do becomes what the agent can do through this server. Authorize it from an account scoped to the work at hand, and keep your client’s approval prompts on.

Verified configurations

Not run by us yet. This profile is Source Validated: the install channel, config entry, credentials and license were checked against the source and upstream metadata, but no configuration has been installed, discovered and executed in a recorded environment. When one is, it appears here with the eight scope dimensions below.

Best for

Engineering teams that want an assistant to investigate a dedicated Sentry organization or project and update issue triage state under explicit human review.

Why use it

It combines first-party Sentry context, trace and issue retrieval with scoped operational actions, and its skills plus organization/project URL constraints give reviewers concrete levers to reduce authority.

Tradeoffs

Production telemetry can contain sensitive application and user data. Triage writes can resolve or assign issues, and the OAuth scope granted upstream can still be broader than the skills this profile advertises. AI-powered search and Seer add model-processing and plan considerations when enabled. The source is licensed FSL-1.1-ALv2 (Functional Source License with a future Apache-2.0 conversion) — source-available, not OSI-approved open source.

Upstream state

repository active · in the official MCP Registry (active). Lifecycle is derived from a committed upstream snapshot at build time, never authored by hand.

Official MCP Registry name: io.github.getsentry/sentry-mcp

Editorial review

Reviewed byOpenSourcesAI EditorialLast updatedAugust 2026SourcesSentry MCP source and remote setup; Sentry MCP skill authorization and stdio package; Sentry MCP security architecture; Sentry MCP architecture; Sentry MCP Functional Source License; Official MCP Registry — Sentry

Grade B — Source Validated. Re-review is due by 2027-02-18. Config entries, credential names and package status can change upstream; verify against the source repository before granting an agent access.

Sources

Related guides

All MCP servers →