Skip to main content
Connecting Sentry lets Claude pull errors and stack traces into incident threads in any channel where the connector is on. Claude connects with its own credential, not a person’s. Pair this connector with the Sentry plugin from Anthropic’s plugin marketplace so Claude knows how to call the API. This connector calls Sentry’s HTTP API. It isn’t an MCP server or a member’s personal claude.ai connector.

​
Create the credential in Sentry

Create an internal-integration token in Sentry (Settings → Developer Settings → Internal Integrations) rather than a user auth token; scope it to the projects Claude should read. Prefer an internal-integration token over a user auth token so access is not tied to a person. Sentry’s own guide for creating the credential is at docs.sentry.io.

​
Add the connector

Go to Organization settings > Claude Tag > Connectors, click Add, and select Sentry. Fill in these fields in the connect form. Self-hosted Sentry uses your own hostname instead of sentry.io. If the connect form offers to include the Sentry plugin, leave that box selected; otherwise add the plugin on the Skills and plugins tab. The first credential you add for a service from the Connectors tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see where a new connector applies before you save the connector. Click Connect to save the connector. The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See how Agent Proxy works.

​
Verify the connection

In a channel where the connector is on, in a new thread:
Sentry appears in the list once the connector is live. New threads pick up the connector on their own; in an existing thread, ask Claude to use the service by name.