sentry
Query Sentry issues, events, releases, alerts, and monitors.
The sentry command provides both direct resource operations and natural-language incident triage through clanker sentry ask.
Usage
bash
clanker sentry [command]Alias: sn
Authentication
yaml
sentry:
auth_token: ""
org_slug: ""
default_project: ""
host: "sentry.io"Environment variables:
| Variable | Description |
|---|---|
SENTRY_AUTH_TOKEN | Sentry User Auth Token |
SENTRY_ORG | Sentry organization slug |
SENTRY_PROJECT | Default project slug |
SENTRY_HOST | Sentry host; defaults to sentry.io |
Recommended token scopes depend on the operation. Read-only triage needs org/project/event read scopes. Mutating commands such as resolve, ignore, assign, monitor mute, and alert deletion need the corresponding write/admin scopes.
Commands
| Command | Description |
|---|---|
ask | Ask natural-language questions about your Sentry organization |
list | List resources such as issues, projects, teams, releases, monitors, or alerts |
get | Get a single Sentry resource |
resolve | Mark one or more issues as resolved |
ignore | Mark one or more issues as ignored |
assign | Assign an issue to a user |
monitor | Manage Sentry Crons monitors |
alert | Manage Sentry alert rules |
Examples
bash
clanker sentry list issues --unresolved --period 24h --project api
clanker sentry get issue PROJECT-123
clanker sentry resolve PROJECT-123 PROJECT-456
clanker sentry monitor checkins nightly-jobNatural-language triage:
bash
clanker sentry ask "what is the worst error today?"
clanker sentry ask "any new errors since the last release?" --project api
clanker sentry ask "are any monitors failing?"
clanker sentry ask "show unresolved issues in prod" --environment prodask gathers relevant Sentry data concurrently and keeps per-org conversation history for follow-up questions.
MCP
The MCP server exposes Sentry tools including:
clanker_sentry_askclanker_sentry_list_issuesclanker_sentry_get_issueclanker_sentry_resolve_issuesclanker_sentry_list_releases
See mcp for transport setup.