All integrations

Run agents with Sentry

Connect Sentry once, and every run that names it works in Sentry on the account you connected.

Connect SentryOpens Settings → Connections in the console.

What an agent can do in Sentry

Access Sentry error-monitoring data: query issues, errors, events and traces, and use Seer to investigate root causes of bugs.

Skills from Sentry's agent plugin that join every run reaching this server:

Jobs on Rush that use Sentry

How Sentry connects

Sentry is a remote MCP server, published by Sentry, at https://mcp.sentry.dev/mcp. Connecting it signs in through the MCP OAuth flow on Sentry's side.

From Sentry: Sentry's MCP documentation · source code.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names sentry in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Sentry",
  "url": "https://mcp.sentry.dev/mcp"
}

Whose Sentry account the agent uses

Your Sentry connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Sentry, and a run started with an API key uses the Sentry of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Sentry, and that agent's runs use their account and nothing else: never yours, never another user's.

More Observability integrations

Frequently asked questions

How do I connect Sentry to Rush?

Open Settings → Connections in the console and connect Sentry, or send POST /me/connections with {"type":"mcp","name":"Sentry","url":"https://mcp.sentry.dev/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Sentry account?

No. A run gets your Sentry connection only when it names it in connections ("connections": ["sentry"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Sentry?

Access Sentry error-monitoring data: query issues, errors, events and traces, and use Seer to investigate root causes of bugs. 42 published jobs use it; this page lists them.

Which skills come with Sentry?

sentry-create-alert, from Sentry's own agent plugin, pinned to a commit. It joins every run that reaches Sentry's MCP server, inside the run's 96 KiB skills limit.

Keep reading