Can I use Bugsnag as a CLI?

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

Can I expose Bugsnag through MCP?

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

Where are Bugsnag credentials stored?

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

Can I deny write access for Bugsnag MCP tools?

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

productivity

Bugsnag CLI for Shell Scripts

Use the Bugsnag CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API token auth

Submit Bugsnag feedback View package source

Bugsnag CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Bugsnag CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Bugsnag CLI for Shell Scripts
kosmokrator integrations:configure bugsnag --set api_token="$BUGSNAG_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call bugsnag.bugsnag_list_projects '{"limit":1,"offset":1,"q":"example_q"}' --json

Discovery Before Execution

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

kosmo integrations:docs bugsnag --json
kosmo integrations:docs bugsnag.bugsnag_list_projects --json
kosmo integrations:schema bugsnag.bugsnag_list_projects --json
kosmo integrations:search "Bugsnag" --json
kosmo integrations:list --json

Useful Bugsnag CLI Functions

Function	Type	Parameters	Description
`bugsnag.bugsnag_list_projects`	Read	limit, offset, q	List Bugsnag projects visible to the authenticated user. Returns project names and IDs that can be used with other tools.
`bugsnag.bugsnag_get_project`	Read	id	Get details for a single Bugsnag project, including its name, API key, type, and error counts.
`bugsnag.bugsnag_list_errors`	Read	project_id, limit, offset, severity, status, sort	List errors for a Bugsnag project. Supports filtering by severity and status, and sorting by various fields.
`bugsnag.bugsnag_get_error`	Read	id	Get details for a specific Bugsnag error, including its message, severity, context, and stack trace.
`bugsnag.bugsnag_list_events`	Read	project_id, limit, offset, error_id	List events (individual error occurrences) for a Bugsnag project. Optionally filter by a specific error.
`bugsnag.bugsnag_list_collaborators`	Read	org_id, limit, offset	List collaborators (team members) for a Bugsnag organization.
`bugsnag.bugsnag_get_current_user`	Read	none	Get the currently authenticated Bugsnag user, including name, email, and associated organizations.

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 Bugsnag CLI Pages

CI Bugsnag CLI for CI. Cron Jobs Bugsnag CLI for cron jobs. Headless Automation Bugsnag CLI for headless automation. Coding Agents Bugsnag CLI for coding agents.