Can I use Sentry as a CLI?

Yes. KosmoKrator exposes a Sentry CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Sentry through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Sentry tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Sentry credentials stored?

Sentry credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Sentry MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

monitoring

Sentry CLI for Cron Jobs

Use the Sentry CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Sentry feedback View package source

Sentry CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Sentry CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Sentry CLI for Cron Jobs
kosmokrator integrations:configure sentry --set auth_token="$SENTRY_AUTH_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call sentry.sentry_list_projects '{"query":"example_query"}' --json

Discovery Before Execution

Agents and scripts can inspect Sentry docs and schemas before choosing a function.

kosmo integrations:docs sentry --json
kosmo integrations:docs sentry.sentry_list_projects --json
kosmo integrations:schema sentry.sentry_list_projects --json
kosmo integrations:search "Sentry" --json
kosmo integrations:list --json

Useful Sentry CLI Functions

Function	Type	Parameters	Description
`sentry.sentry_list_projects`	Read	query	List all Sentry projects accessible to the authenticated user. Returns project slugs, organization slugs, and platforms for use in other Sentry tools.
`sentry.sentry_get_project`	Read	org_slug, project_slug	Get detailed information about a specific Sentry project, including its slug, platform, team assignments, and error statistics.
`sentry.sentry_list_issues`	Read	org_slug, project_slug, query, sort, limit	List issues (errors) for a specific Sentry project. Supports filtering by status, query, sorting, and time range. Returns issue IDs, titles, counts, and severity.
`sentry.sentry_get_issue`	Read	issue_id	Get detailed information about a specific Sentry issue, including the error message, stacktrace, tags, event count, and affected users.
`sentry.sentry_list_releases`	Read	org_slug, project_slug, limit	List releases for a specific Sentry project. Returns version strings, deployment dates, authors, and commit information.
`sentry.sentry_create_issue`	Write	org_slug, project_slug, title, message, level, tags, extra	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.
`sentry.sentry_get_current_user`	Read	none	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.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Sentry CLI Pages

CI Sentry CLI for CI. Shell Scripts Sentry CLI for shell scripts. Headless Automation Sentry CLI for headless automation. Coding Agents Sentry CLI for coding agents.