Sentry
Read Sentry issues, events and releases so agents can debug production errors.
Connect it with: API key. Sentry's own documentation: https://docs.sentry.io/api/auth/.
What agents can do
Connect Sentry so the agents working your tasks can reach it. With it connected, they can:
- Read the Sentry issue a task names: its stack trace, breadcrumbs, tags and the latest event.
- Find the release and commit that introduced an error, to fix it at the source.
- Check whether an issue still occurs after a deploy.
- Feed post-deploy regression checks with error metrics for a release.
Before you start
- A Sentry organization and the Manager, Admin or Owner role to create an internal integration (any member can create a personal token).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Sentry
Jaah connects to Sentry with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Base URL: https://sentry.io for Sentry SaaS (or https://us.sentry.io / https://de.sentry.io for your data region), or your self-hosted Sentry's address.
- Organization slug: Sentry > Settings > Organization Settings > General > Organization Slug, the acme in https://acme.sentry.io or sentry.io/organizations/acme/.
- Auth token: Sentry > Settings > Developer Settings > Custom Integrations > Create New Integration > Internal Integration: name it Jaah, set Issue & Event Read and Organization Read (add Project Read and Release Read if agents need them), Save, then under Tokens select New Token and copy it. A personal token from User Settings > Personal Tokens with org:read and event:read also works.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Sentry card.
- Name the secret and choose who can use it.
- Fill in Base URL, Organization slug, Auth token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Sentry with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Sentry with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: base_url, org_slug, auth_token.
Tell the agent in your task description which secret to use, for example “use the Sentry secret org/sentry”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Sentry once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Sentry's side too, revoke or delete the key at Sentry.
Limitations
- Sentry's hosted MCP server needs its own sign-in or token, which this secret does not hold: to give agents its tools, add a Custom MCP server secret with the URL https://mcp.sentry.dev/mcp, connect it, and link it to the project.
- An internal integration token is tied to one organization; connect each organization separately.
- A personal token acts as you and sees what you see; an internal integration acts as the organization.
- Sentry's API is rate-limited per token and per organization; very large exports are throttled.
- Agents can do only what the connected Sentry account allows.
Troubleshooting
Test says Sentry rejected the auth token
The token was revoked, mistyped, or belongs to another Sentry host. Create a new token on the internal integration and select Replace; check Base URL matches the Sentry you sign in to.
Test passes but agents get 403 on issues or events
The token lacks Issue & Event Read. Edit the internal integration's permissions; Sentry applies them to existing tokens.
Agents get 404 for the organization
Organization slug is wrong. Copy it from Organization Settings > General.
Still stuck? Select Test and read the result: it names the value Sentry refused and the status it answered.
FAQ
Internal integration or personal token?
Use an internal integration for a team connection: it belongs to the organization and survives a person leaving. A personal token is fine for your own use.
Does it work with self-hosted Sentry?
Yes. Set Base URL to your Sentry's https address and create the token there.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Sentry account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.