Try Bifrost Enterprise free for 14 days.
Request access
[ HTTP MCP ]

How to Use Sentry MCP Server with Bifrost

Use Sentry’s MCP server to investigate errors, issues, traces, and application health from AI coding assistants.

[ MCP SERVER SUMMARY ]

Sentry MCP server summary

Sentry's MCP service helps coding agents investigate errors, issues, traces, and application health. Use the hosted remote endpoint or STDIO for self-hosted Sentry. Bifrost governs which Sentry tools each engineer can call and logs every debug action.

PropertyDetails
CompanySentry
Connection typeHTTP
AuthenticationOAuth or Sentry user auth token
Package or endpointhttps://mcp.sentry.dev/mcp
CapabilitiesIssue and error investigation, Trace and performance tools, Seer and triage skills
Official documentationSentry MCP documentation

Before you start

  • A Sentry org
  • OAuth via mcp.sentry.dev or a user auth token for STDIO/header auth

What you can do with Sentry

  • Let coding agents pull stack traces during PR review through Bifrost
  • Use Sentry-Bearer header auth for remote clients that support custom headers
  • Disable Seer skills on self-hosted if unsupported
ObservabilityDeveloper Tools

[ HOW TO CONNECT ]

Connect Sentry to Bifrost in three steps

1

Install Bifrost

Start the gateway locally or deploy in your VPC.

npx -y @maximhq/bifrost
2

Add Sentry in MCP Gateway

Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.

• Hosted: https://mcp.sentry.dev/mcp with OAuth.

• STDIO alternative: npx @sentry/mcp-server@latest --access-token=... for self-hosted.

• Header auth may use Authorization: Sentry-Bearer <token> (not standard Bearer).

3

Point clients at Bifrost /mcp

Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Sentry.

{
  "mcpServers": {
    "bifrost": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer vk_your_virtual_key"
      }
    }
  }
}

[ EXAMPLE CONFIG ]

Register Sentry via API

Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.

curl -X POST http://localhost:8080/api/mcp/client \
  -H "Content-Type: application/json" \
  -d '{
    "name": "sentry",
    "connection_type": "http",
    "connection_string": "https://mcp.sentry.dev/mcp",
    "auth_type": "oauth",
    "tools_to_execute": [
      "*"
    ]
  }'

[ WHY BIFROST ]

Run Sentry through one governed gateway

Access control

Virtual keys, RBAC, and tool allowlists per team or agent.

Cost governance

Attribute MCP tool spend alongside LLM usage in one view.

Observability

Log every tool call with latency, server, and virtual key metadata.

Credential isolation

Upstream secrets stay in the gateway — not on every laptop.

[ FAQ ]

Common questions

What does the Sentry MCP server do?

Sentry exposes issue and error investigation, trace and performance tools, seer and triage skills to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.

How does Sentry authenticate when used with Bifrost?

Sentry uses OAuth or Sentry user auth token. Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.

Can Claude Desktop, Cursor, or Claude Code use Sentry through Bifrost?

Yes. After registering Sentry in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.

[ MCP GATEWAY ]

One gateway for Sentry and every other MCP server

Bifrost MCP Gateway gives you tool-level access control, audit logs, and up to 92% lower token costs when agents orchestrate multiple tools.