Sentry MCP Server

Sentry MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. An MCP server for self-hosted sentry.

What you get

A Model Context Protocol (MCP) server designed specifically for interacting with self-hosted Sentry instances.

This server provides tools to retrieve information and perform actions on issues within a self-hosted Sentry setup. It reads the Sentry instance URL, authentication token, and organization slug from environment variables.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Sentry is connected, these are the calls the assistant has available:

• Description — Retrieve details for a specific Sentry issue by ID or URL
• Input — { "issue_id_or_url": "string" } (e.g., "12345" or "https://sentry.example.com/organizations/org/issues/12345/")

Configuration and credentials

You will need 5 environment variables: SENTRY_URL, SENTRY_AUTH_TOKEN, SENTRY_ORG_SLUG, YOUR_SENTRY_URL, YOUR_SENTRY_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sentry mcp server does with a few real requests.

Choosing this one

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sentry's toolset — Description, Input — is a fair guide to whether it matches your workflow. It is maintained by ddfourtwo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Sentry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.