KosmoKrator

monitoring

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.

5 functions 3 read 2 write API key auth
Submit Atlassian Statuspage feedback View package source

Atlassian Statuspage CLI Setup

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

# 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 use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

KeyEnv varTypeRequiredLabel
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

Call Atlassian Statuspage Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

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

Use the provider shortcut form for shorter human-facing commands.

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

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities 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

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Atlassian Statuspage.

statuspage.statuspage_list_incidents

Read read

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

Parameters
limit, page

Generic CLI call

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

Provider shortcut

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

statuspage.statuspage_create_incident

Write write

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

Parameters
name, status, impact, body, component_ids

Generic CLI 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"}' --json

Provider shortcut

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

statuspage.statuspage_update_incident

Write write

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

Parameters
id, name, status, impact, body, component_ids

Generic CLI 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"}' --json

Provider 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"}' --json

statuspage.statuspage_list_components

Read read

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

Parameters
page, per_page

Generic CLI call

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

Provider shortcut

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

statuspage.statuspage_get_current_user

Read read

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

Parameters
none

Generic CLI call

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

Provider shortcut

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

Function Schemas

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

statuspage.statuspage_list_incidents

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

Operation
Read read
Schema command
kosmo integrations:schema statuspage.statuspage_list_incidents --json
ParameterTypeRequiredDescription
limit integer no Maximum number of incidents to return per page.
page integer no Page number for pagination (1-based).

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.

Operation
Write write
Schema command
kosmo integrations:schema statuspage.statuspage_create_incident --json
ParameterTypeRequiredDescription
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.

statuspage.statuspage_update_incident

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

Operation
Write write
Schema command
kosmo integrations:schema statuspage.statuspage_update_incident --json
ParameterTypeRequiredDescription
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.

statuspage.statuspage_list_components

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

Operation
Read read
Schema command
kosmo integrations:schema statuspage.statuspage_list_components --json
ParameterTypeRequiredDescription
page integer no Page number for pagination (1-based).
per_page integer no Number of components to return per page.

statuspage.statuspage_get_current_user

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

Operation
Read read
Schema command
kosmo integrations:schema statuspage.statuspage_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

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.