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.

productivity

Atlassian Statuspage CLI for AI Agents

Use the Atlassian Statuspage CLI from KosmoKrator to call Atlassian Statuspage tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Atlassian Statuspage CLI Setup

Atlassian Statuspage can be configured headlessly with `kosmokrator integrations:configure statuspage`.

Install, configure, and verify

# 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 statuspage --set api_key="$STATUSPAGE_API_KEY" --set page_id="$STATUSPAGE_PAGE_ID" --enable --read allow --write ask --json
kosmokrator integrations:doctor statuspage --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`api_key`	`STATUSPAGE_API_KEY`	Secret `secret`	yes	API Key
`page_id`	`STATUSPAGE_PAGE_ID`	Text `string`	yes	Page ID
`url`	`STATUSPAGE_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call statuspage.statuspage_get_current_user '{}' --json

Provider shortcut

kosmo integrations:statuspage statuspage_get_current_user '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

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

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`statuspage.statuspage_get_current_user`

Get the currently authenticated Atlassian Statuspage user. Useful for verifying API credentials and checking user permissions.

Read read

Parameters: none

Generic call

kosmo integrations:call statuspage.statuspage_get_current_user '{}' --json

Shortcut

kosmo integrations:statuspage statuspage_get_current_user '{}' --json

`statuspage.statuspage_list_pages`

List Atlassian Statuspage pages available to the authenticated API key. Use this to discover page IDs.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call statuspage.statuspage_list_pages '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:statuspage statuspage_list_pages '{"page":1,"per_page":1}' --json

`statuspage.statuspage_get_page`

Get details for the configured Atlassian Statuspage page, or a supplied page ID visible to the API key.

Read read

Parameters: page_id

Generic call

kosmo integrations:call statuspage.statuspage_get_page '{"page_id":"example_page_id"}' --json

Shortcut

kosmo integrations:statuspage statuspage_get_page '{"page_id":"example_page_id"}' --json

`statuspage.statuspage_list_incidents`

List all incidents for your Atlassian Statuspage. Returns scheduled, ongoing, and resolved incidents with their current status and impact.

Read read

Parameters: limit, page, q

Generic call

kosmo integrations:call statuspage.statuspage_list_incidents '{"limit":1,"page":1,"q":"example_q"}' --json

Shortcut

kosmo integrations:statuspage statuspage_list_incidents '{"limit":1,"page":1,"q":"example_q"}' --json

`statuspage.statuspage_list_unresolved_incidents`

List unresolved incidents for the configured Atlassian Statuspage page.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call statuspage.statuspage_list_unresolved_incidents '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:statuspage statuspage_list_unresolved_incidents '{"page":1,"limit":1}' --json

`statuspage.statuspage_list_upcoming_incidents`

List upcoming scheduled incidents and maintenance windows for the configured Atlassian Statuspage page.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call statuspage.statuspage_list_upcoming_incidents '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:statuspage statuspage_list_upcoming_incidents '{"page":1,"limit":1}' --json

`statuspage.statuspage_create_incident`

Create a new incident on your Atlassian Statuspage. Specify the incident name, status, impact level, and an optional body describing the issue.

Write write

Parameters: name, status, impact, body, component_ids, scheduled_for, scheduled_until

Generic call

kosmo integrations:call statuspage.statuspage_create_incident '{"name":"example_name","status":"example_status","impact":"example_impact","body":"example_body","component_ids":"example_component_ids","scheduled_for":"example_scheduled_for","scheduled_until":"example_scheduled_until"}' --json

Shortcut

kosmo integrations:statuspage statuspage_create_incident '{"name":"example_name","status":"example_status","impact":"example_impact","body":"example_body","component_ids":"example_component_ids","scheduled_for":"example_scheduled_for","scheduled_until":"example_scheduled_until"}' --json

`statuspage.statuspage_update_incident`

Update an existing incident on your Atlassian Statuspage. Change the status, add updates to the body, or modify impact level.

Write write

Parameters: id, name, status, impact, body, component_ids, scheduled_for, scheduled_until

Generic call

kosmo integrations:call statuspage.statuspage_update_incident '{"id":"example_id","name":"example_name","status":"example_status","impact":"example_impact","body":"example_body","component_ids":"example_component_ids","scheduled_for":"example_scheduled_for","scheduled_until":"example_scheduled_until"}' --json

Shortcut

kosmo integrations:statuspage statuspage_update_incident '{"id":"example_id","name":"example_name","status":"example_status","impact":"example_impact","body":"example_body","component_ids":"example_component_ids","scheduled_for":"example_scheduled_for","scheduled_until":"example_scheduled_until"}' --json

`statuspage.statuspage_delete_incident`

Delete an incident from the configured Atlassian Statuspage page. Resolving is usually preferable for real incidents.

Write write

Parameters: id

Generic call

kosmo integrations:call statuspage.statuspage_delete_incident '{"id":"example_id"}' --json

Shortcut

kosmo integrations:statuspage statuspage_delete_incident '{"id":"example_id"}' --json

`statuspage.statuspage_list_components`

List all components on your Atlassian Statuspage. Returns component names, current status, and group information.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call statuspage.statuspage_list_components '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:statuspage statuspage_list_components '{"page":1,"per_page":1}' --json

`statuspage.statuspage_get_component`

Get a single component from the configured Atlassian Statuspage page by component ID.

Read read

Parameters: id

Generic call

kosmo integrations:call statuspage.statuspage_get_component '{"id":"example_id"}' --json

Shortcut

kosmo integrations:statuspage statuspage_get_component '{"id":"example_id"}' --json

`statuspage.statuspage_create_component`

Create a component on the configured Atlassian Statuspage page.

Write write

Parameters: name, status, description, group_id, only_show_if_degraded, showcase

Generic call

kosmo integrations:call statuspage.statuspage_create_component '{"name":"example_name","status":"example_status","description":"example_description","group_id":"example_group_id","only_show_if_degraded":true,"showcase":true}' --json

Shortcut

kosmo integrations:statuspage statuspage_create_component '{"name":"example_name","status":"example_status","description":"example_description","group_id":"example_group_id","only_show_if_degraded":true,"showcase":true}' --json

`statuspage.statuspage_update_component`

Update an existing component on the configured Atlassian Statuspage page.

Write write

Parameters: id, name, status, description, group_id, only_show_if_degraded, showcase

Generic call

kosmo integrations:call statuspage.statuspage_update_component '{"id":"example_id","name":"example_name","status":"example_status","description":"example_description","group_id":"example_group_id","only_show_if_degraded":true,"showcase":true}' --json

Shortcut

kosmo integrations:statuspage statuspage_update_component '{"id":"example_id","name":"example_name","status":"example_status","description":"example_description","group_id":"example_group_id","only_show_if_degraded":true,"showcase":true}' --json

`statuspage.statuspage_delete_component`

Delete a component from the configured Atlassian Statuspage page.

Write write

Parameters: id

Generic call

kosmo integrations:call statuspage.statuspage_delete_component '{"id":"example_id"}' --json

Shortcut

kosmo integrations:statuspage statuspage_delete_component '{"id":"example_id"}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

statuspage.statuspage_get_current_user 0 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_get_current_user --json

Parameter	Type	Required	Description
No parameters.

statuspage.statuspage_list_pages 2 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_list_pages --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (1-based).
`per_page`	integer	no	Number of pages to return per page.

statuspage.statuspage_get_page 1 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_get_page --json

Parameter	Type	Required	Description
`page_id`	string	no	Optional page ID. Defaults to the configured Page ID.

statuspage.statuspage_list_incidents 3 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_list_incidents --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of incidents to return per page.
`page`	integer	no	Page number for pagination (1-based).
`q`	string	no	Optional search query supported by the Statuspage API.

statuspage.statuspage_list_unresolved_incidents 2 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_list_unresolved_incidents --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (1-based).
`limit`	integer	no	Maximum number of incidents to return per page.

statuspage.statuspage_list_upcoming_incidents 2 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_list_upcoming_incidents --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (1-based).
`limit`	integer	no	Maximum number of incidents to return per page.

statuspage.statuspage_create_incident 7 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_create_incident --json

Parameter	Type	Required	Description
`name`	string	yes	A short title for the incident (e.g. "API Latency in EU Region").
`status`	string	yes	Incident status. One of: "investigating", "identified", "monitoring", "resolved", "scheduled", "in_progress", "verifying", "completed".
`impact`	string	yes	The impact level of the incident. One of: "none", "minor", "major", "critical".
`body`	string	no	A detailed description of the incident and current status.
`component_ids`	array	no	Array of component IDs affected by this incident.
`scheduled_for`	string	no	Optional ISO-8601 start time for scheduled maintenance.
`scheduled_until`	string	no	Optional ISO-8601 end time for scheduled maintenance.

statuspage.statuspage_update_incident 8 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_update_incident --json

Parameter	Type	Required	Description
`id`	string	yes	The incident ID to update.
`name`	string	no	Updated incident title.
`status`	string	no	Updated incident status. One of: "investigating", "identified", "monitoring", "resolved", "scheduled", "in_progress", "verifying", "completed".
`impact`	string	no	Updated impact level. One of: "none", "minor", "major", "critical".
`body`	string	no	Updated incident body describing the latest status.
`component_ids`	array	no	Updated array of component IDs affected by this incident.
`scheduled_for`	string	no	Updated ISO-8601 start time for scheduled maintenance.
`scheduled_until`	string	no	Updated ISO-8601 end time for scheduled maintenance.

statuspage.statuspage_delete_incident 1 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_delete_incident --json

Parameter	Type	Required	Description
`id`	string	yes	The incident ID to delete.

statuspage.statuspage_list_components 2 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_list_components --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (1-based).
`per_page`	integer	no	Number of components to return per page.

statuspage.statuspage_get_component 1 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_get_component --json

Parameter	Type	Required	Description
`id`	string	yes	The component ID to fetch.

statuspage.statuspage_create_component 6 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_create_component --json

Parameter	Type	Required	Description
`name`	string	yes	Component name shown on the status page.
`status`	string	no	Initial component status.
`description`	string	no	Optional component description.
`group_id`	string	no	Optional component group ID.
`only_show_if_degraded`	boolean	no	Whether to hide the component unless degraded.
`showcase`	boolean	no	Whether to show this component prominently.

statuspage.statuspage_update_component 7 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_update_component --json

Parameter	Type	Required	Description
`id`	string	yes	The component ID to update.
`name`	string	no	Updated component name.
`status`	string	no	Updated component status.
`description`	string	no	Updated component description.
`group_id`	string	no	Updated component group ID.
`only_show_if_degraded`	boolean	no	Whether to hide the component unless degraded.
`showcase`	boolean	no	Whether to show this component prominently.

statuspage.statuspage_delete_component 1 parameters

Schema command

kosmo integrations:schema statuspage.statuspage_delete_component --json

Parameter	Type	Required	Description
`id`	string	yes	The component ID to delete.

Permissions

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.