Use the Sentry CLI from KosmoKrator to call Sentry tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Sentry can be configured headlessly with `kosmokrator integrations:configure sentry`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure sentry --set auth_token="$SENTRY_AUTH_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor sentry --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API tokenapi_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
auth_token
SENTRY_AUTH_TOKEN
Secret secret
yes
Auth Token
url
SENTRY_URL
URL url
no
Sentry API URL
Call Sentry Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Sentry.
sentry.sentry_list_projects
Read read
List all Sentry projects accessible to the authenticated user. Returns project slugs, organization slugs, and platforms for use in other Sentry tools.
List issues (errors) for a specific Sentry project. Supports filtering by status, query, sorting, and time range. Returns issue IDs, titles, counts, and severity.
Create a new issue (user report or crash report) in a Sentry project. Requires the error message and optional metadata like stacktrace, tags, and user context.
Parameters
org_slug, project_slug, title, message, level, tags, extra
Get the currently authenticated Sentry user. Returns user name, email, and organization memberships. Useful for verifying the connection and identifying which Sentry account is being used.
List issues (errors) for a specific Sentry project. Supports filtering by status, query, sorting, and time range. Returns issue IDs, titles, counts, and severity.
Maximum number of releases to return (default: 25, max: 100).
sentry.sentry_create_issue
Create a new issue (user report or crash report) in a Sentry project. Requires the error message and optional metadata like stacktrace, tags, and user context.
Short description of the issue (the error message or title).
message
string
no
Full error message or stacktrace.
level
string
no
Severity level: "fatal", "error", "warning", "info", or "debug". Defaults to "error".
tags
object
no
Key-value tags to attach to the issue (e.g., {"environment": "production", "version": "1.0.0"}).
extra
object
no
Additional context data as key-value pairs.
sentry.sentry_get_current_user
Get the currently authenticated Sentry user. Returns user name, email, and organization memberships. Useful for verifying the connection and identifying which Sentry account is being used.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.