@kody/sentry
Inspect Sentry organizations, projects, issues, and events with a saved auth token.
OtherTopics: sentry, debugging, issues, observability, agents, openapi
- Version
- 1.0.0
- License
- MIT
- Published
- September 10, 2026
- Pinned commit
3578fba- Rating
- No ratings yet
- Forks
- 2
- Adaptation effort
- —
README
Agent docs@kody/sentry
Intent
Headless Sentry utilities for Kody workflows — organizations, projects, issue
search, event summaries, and agent-ready triage using a user-scoped
sentryAuthToken secret. The low-level REST layer is a thin OpenAPI-scaffolded
client (listorganizations, listorganizationprojects,
listorganizationissues) plus a small escape-hatch request helper for
endpoints missing from Sentry's public OpenAPI inventory (for example latest
issue event). Writes through request default to dry-run.
This listing is meant to be forked. The live @kody/sentry package does not
talk to a shared Sentry org. After you fork, save your own auth token and call
the helpers in your account.
This official API-token package is the preferred invoke path. Setup is
harder: save a user-scoped sentryAuthToken. For a faster first win, connect
Sentry MCP in Get started and use
@kody/sentry-mcp.
What it does
- List organizations or projects before querying issues
- Search unresolved issues with optional latest-event summaries for triage
- Inspect a specific issue, its events, or build a full triage bundle
- Call uncommon Sentry REST endpoints via
request(mutating calls default todryRun)
Prerequisites / setup
Auth is a bearer auth token (personal token, organization token, or internal-integration token). This is not OAuth by default and not a bot token. Do not paste the token into chat.
- Create a token in Sentry: User settings → Personal Tokens or an internal integration.
- Grant at least
org:read,project:read, andevent:read. Addevent:writeonly if you will call mutatingrequestpaths. - Save it as
sentryAuthToken:
- Approve hosts
sentry.io,us.sentry.io, andde.sentry.ioon that secret. Saving the secret does not approve hosts by itself.
Optional BYO OAuth
Only if you already have a Sentry OAuth application. Redirect URI must be
exactly https://kody.codes/connect/oauth. Do not register a new platform
OAuth app for Kody.
After connect, pass integration: 'sentry' (or another saved integration
name) on every call.
Multi-account
There are no hard-coded account aliases:
- Token lane: pass
secretName(defaultsentryAuthToken). Save a second token assentryAuthTokenWorkand passsecretName: 'sentryAuthTokenWork'. - OAuth lane: pass
integration(for example'sentry'or'sentry-work').
Scopes and 403s
| Scope | Used for |
|---|---|
org:read | list-organizations and org-scoped reads |
project:read | list-projects, resolve-project |
event:read | issues and events |
event:write | mutating request paths (resolve/ignore/assign) |
A 403 from this package names the missing likely scope and the next setup
step (recreate the token with that scope, then update the secret). A 401
means the token is missing or invalid — reopen the secrets URL above.
Hosts
Default API host is sentry.io. Approve the host(s) you will call on that
secret:
| Host | When to approve |
|---|---|
sentry.io | Default SaaS API host (start here) |
us.sentry.io | US data-storage region |
de.sentry.io | EU data-storage region |
Pass host on any export to target a region or self-hosted instance
(host: "us.sentry.io" or host: "sentry.example.com"). Self-hosted hosts
must be added to the secret's allowed hosts after save. Requests are always
HTTPS.
Docs: Choosing the API base domain · Authentication
Agents: import paths, smoke checks, dry-run write snippets, and edge cases live
in AGENTS.md.
Done when
sentryAuthTokenis saved and needed hosts are approved (or OAuth connected)- Smoke test returns live org list (or clear setup when the secret is missing)
- Issue search / get-issue / triage-issue succeed against a known issue id
- Mutating
requestpaths preview with dry-run until you passdryRun: false
Forking
Community listings are snapshots. Fork this listing into your account, review
the source, publish your copy, then save sentryAuthToken. Do not treat the
live @kody/sentry package as bound to your org.
One-click listing URL after publish: https://kody.codes/@kody/sentry
Branding
The community icon is Sentry's official glyph from the public Sentry branding page (glyph, light-on-dark). The path is unmodified. Sentry® and the Sentry glyph are trademarks of Functional Software, Inc. This package is not affiliated with or endorsed by Functional Software, Inc. (Sentry).
Report this listing
Log in to report this listing.