Skip to content

Sentry MCP connector

The Sentry connector brings error events, tags, dashboards, saved queries and team membership into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about what is breaking inside their own Sentry access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Sentry to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Sentry once

  1. Open Connections, choose Add connection, and pick Sentry.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Sentry API key. One person generates a token in Sentry and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

sentry
Sentry
Apache Airflow
Boomi
Browserbase
Caspio
Cloudflare
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Sentry MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Sentry MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Sentry MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Sentry to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Sentry through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Find out what broke overnight

    Ask which events fired in the last twelve hours, grouped by tag, and get the answer without opening a single Sentry dashboard.

  • Support

    Check Sentry before replying to a customer

    Paste a customer's error message and ask whether Sentry has seen it recently, so the reply is based on what actually happened rather than a guess.

  • Product

    See which release generated the most events

    Ask for events broken down by release or environment tag to decide whether a rollout should pause.

  • Platform

    Build a dashboard from a plain request

    Describe the dashboard you want, for one service or one environment, and have it created in Sentry with the widgets you named.

  • Engineering managers

    Tidy up saved queries and dashboards

    Find stale saved Discover queries and dashboards across the organization and update or remove them in one pass.

  • IT

    Keep Sentry team membership current

    Ask who is on which Sentry team, add a new hire to the right teams, and remove people who have moved on.

Try asking

  • “Which Sentry events fired in production since midnight?”
  • “Break down this week's events by release tag”
  • “Add the new backend hires to the Payments Sentry team”

See all 239 Sentry tools below

AI tools

Sentry tools for your AI agents

239 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sentry, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 212 of 239 Sentry tools here. Connect Sentry and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting Sentry gets you

6 screens from the product, each doing one job for your Sentry account.

The agent

Ask about Sentry events in plain language.

Live answers from Sentry events, tags and dashboards, no query syntax required.

  • events
  • tags
  • dashboards
  • teams

Ask Elaichi to work across your apps.

Which Sentry events fired in production since midnight?

Break down this week's events by release tag

Add the new backend hires to the Payments Sentry team

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Sentry endpoint for every AI client.

Claude, ChatGPT and Cursor reach Sentry through one governed endpoint, no SDK, no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

239 Sentry tools, no custom code to write.

Events, tags, dashboards, saved queries, users and teams, covered without an engineer building anything.

  • List all Sentry users
  • Get single Sentry user by ID
  • Delete a Sentry user by ID
  • Sentry 0 organizations attach member
ElaichiTools
Tool Action Description
List all Sentry users List List all members of a Sentry organization, including pending invites that have been approved by owners or managers but not yet accepted by the invitee. Returns: externalUsers, id, email, name, user, orgRole, pending, expired, flags, dateCreated, inviteStatus, inviterName. Required: project_id_or_slug.
Get single Sentry user by ID Get Get a single Sentry organization member by id, including team memberships, the linked user account, and role lists; returns a pending invite if it has been approved but not yet accepted. Returns: externalUsers, role, roleName, id, email, name, user, orgRole, pending, expired, flags, dateCreated, inviteStatus, inviterName, teams, teamRoles, invite_link, isOnlyOwner, orgRoleList, teamRoleList,…
Delete a Sentry user by ID Delete Delete a Sentry organization member (user) from an organization by id. Returns an empty 204 response on success. Required: id.
Sentry 0 organizations attach member Action Add or invite a member to a Sentry organization. Returns the created member including id, email, name, orgRole, pending, expired, inviteStatus, and nested user details. Required: email.
Get single Sentry 0 organization by ID Get Get a single Sentry organization by id. Returns the organization's id, slug, name, status, dateCreated, avatar, links, and access flags (allowMemberInvite, allowMemberProjectCreation, allowSuperuserAccess). Required: id.

Toolboxes

Every team gets its own Sentry toolbox.

Support reads events while Platform manages dashboards, each team scoped to its own work.

  • Engineering
  • Support
  • Platform
  • Product
ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Sentry · events and tags

Sentry starter 18 Mar 4, 2026

Support toolbox

Sentry · customer-facing errors

— 9 Mar 2, 2026

Platform toolbox

Sentry · dashboards and saved queries

— 24 Feb 27, 2026

Product toolbox

Sentry · release health

Sentry starter 6 Feb 19, 2026

IT toolbox

Sentry · users and team membership

— 31 Jan 30, 2026

Leadership toolbox

Sentry · organization dashboards

— 12 Jan 22, 2026

Shared connections

Share Sentry access without sharing the key.

One person connects Sentry, teams work through it, and nobody else sees the credential.

  • Production
  • Staging
  • Web
  • Mobile
ElaichiConnections
Connection Scope Status Access
SE

Sentry (Production)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
SE

Sentry (Staging)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
SE

Sentry (Web)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
SE

Sentry (Mobile)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
SE

Sentry (Backend)

Connected by Clara Nowak

Personal • Active Not shared
SE

Sentry (Support)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Know who touched which Sentry dashboard.

Every call names the person, the action, the type and the Sentry resource it reached.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Sentry Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Sentry Events Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Sentry Events List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Sentry events into work.

Events are fetched, grouped, drafted into a digest, approved by a person, then posted back.

Sentry digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch events

    Sentry

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Sentry

    Queued

Collections and dashboards

Sentry health numbers, refreshed on a schedule.

Events created over 14 days, broken down by team, computed with no model involved.

Sentry health

Refreshed 4 minutes ago · every 15 minutes · from the events collection

Live

Events

1,284 ↓ 12%

Tags

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Events created

Last 14 days

By team

Share of activity

Production 34%

Staging 27%

Web 21%

Mobile 18%

FAQ

Frequently asked questions

How do I connect Sentry to Claude?

Connect Sentry in Elaichi first: paste a Sentry API key when asked, and the connection is live. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi and Sentry is available from that point.

Does Sentry work with ChatGPT and Cursor as well as Claude?

Yes. Once Sentry is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor or any other MCP client. You connect Sentry once and every client you use picks it up.

What can an AI agent actually do with my Sentry data?

With Sentry connected, an agent can list recent events in an organization, break them down by tag such as release or environment, look up a specific user, and read or create dashboards and saved Discover queries. It can also show who is on which Sentry team and add or remove members. Short, concrete asks such as "events tagged production since midnight" work better than long paragraphs.

Does connecting Sentry give the AI everything in my organization?

No. Every call to Sentry runs as the person who signed in, so the agent sees only the organizations, projects and events that person can already open in Sentry. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Sentry itself allows.

Can my team share one Sentry connection?

Yes. One person connects Sentry with an API key in Elaichi and shares the connection with a team, and nobody else ever handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who asked Sentry for what.

Can I stop an agent from deleting or changing things in Sentry?

Yes. Restrictions in Elaichi apply per action, so you can allow reading events and dashboards in Sentry while blocking deletion of users, dashboards or saved queries. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Sentry connection when someone leaves?

Offboarding a person in Elaichi ends their access to Sentry through every client at once. If they connected a Sentry account that was shared with a team, the shared connection keeps working for everyone else. Disconnecting Sentry once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Sentry MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Sentry is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put Sentry in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.