Can I use Atlassian Statuspage as a CLI?

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

Can I expose Atlassian Statuspage through MCP?

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

Where are Atlassian Statuspage credentials stored?

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

Can I deny write access for Atlassian Statuspage MCP tools?

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

monitoring

Atlassian Statuspage CLI for Cron Jobs

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

5 functions 3 read 2 write API key auth

Submit Atlassian Statuspage feedback View package source

Atlassian Statuspage 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 Atlassian Statuspage CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Atlassian Statuspage CLI for Cron Jobs
kosmokrator integrations:configure statuspage --set api_key="$STATUSPAGE_API_KEY" --set page_id="$STATUSPAGE_PAGE_ID" --enable --read allow --write ask --json
kosmo integrations:call statuspage.statuspage_list_incidents '{"limit":1,"page":1}' --json

Discovery Before Execution

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

kosmo integrations:docs statuspage --json
kosmo integrations:docs statuspage.statuspage_list_incidents --json
kosmo integrations:schema statuspage.statuspage_list_incidents --json
kosmo integrations:search "Atlassian Statuspage" --json
kosmo integrations:list --json

Useful Atlassian Statuspage CLI Functions

Function	Type	Parameters	Description
`statuspage.statuspage_list_incidents`	Read	limit, page	List all incidents for your Atlassian Statuspage. Returns scheduled, ongoing, and resolved incidents with their current status and impact.
`statuspage.statuspage_create_incident`	Write	name, status, impact, body, component_ids	Create a new incident on your Atlassian Statuspage. Specify the incident name, status, impact level, and an optional body describing the issue.
`statuspage.statuspage_update_incident`	Write	id, name, status, impact, body, component_ids	Update an existing incident on your Atlassian Statuspage. Change the status, add updates to the body, or modify impact level.
`statuspage.statuspage_list_components`	Read	page, per_page	List all components on your Atlassian Statuspage. Returns component names, current status, and group information.
`statuspage.statuspage_get_current_user`	Read	none	Get the currently authenticated Atlassian Statuspage user. Useful for verifying API credentials and checking user permissions.

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 Atlassian Statuspage CLI Pages

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