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 MCP, CLI, and Lua Integration for AI Agents

Atlassian Statuspage integration docs for AI agents: MCP gateway setup, Atlassian Statuspage CLI commands, Lua API reference, credentials, and function schemas.

Atlassian Statuspage for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Atlassian Statuspage CLIHeadless setup, JSON output, direct function calls. Atlassian Statuspage MCPExpose selected tools to local MCP clients. Atlassian Statuspage LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: statuspage
route_slug: statuspage
package: statuspage
auth_strategy: api_key
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`statuspage.statuspage_get_current_user`	Read `read`	0	Get the currently authenticated Atlassian Statuspage user. Useful for verifying API credentials and checking user permissions.
`statuspage.statuspage_list_pages`	Read `read`	2	List Atlassian Statuspage pages available to the authenticated API key. Use this to discover page IDs.
`statuspage.statuspage_get_page`	Read `read`	1	Get details for the configured Atlassian Statuspage page, or a supplied page ID visible to the API key.
`statuspage.statuspage_list_incidents`	Read `read`	3	List all incidents for your Atlassian Statuspage. Returns scheduled, ongoing, and resolved incidents with their current status and impact.
`statuspage.statuspage_list_unresolved_incidents`	Read `read`	2	List unresolved incidents for the configured Atlassian Statuspage page.
`statuspage.statuspage_list_upcoming_incidents`	Read `read`	2	List upcoming scheduled incidents and maintenance windows for the configured Atlassian Statuspage page.
`statuspage.statuspage_create_incident`	Write `write`	7	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 `write`	8	Update an existing incident on your Atlassian Statuspage. Change the status, add updates to the body, or modify impact level.
`statuspage.statuspage_delete_incident`	Write `write`	1	Delete an incident from the configured Atlassian Statuspage page. Resolving is usually preferable for real incidents.
`statuspage.statuspage_list_components`	Read `read`	2	List all components on your Atlassian Statuspage. Returns component names, current status, and group information.
`statuspage.statuspage_get_component`	Read `read`	1	Get a single component from the configured Atlassian Statuspage page by component ID.
`statuspage.statuspage_create_component`	Write `write`	6	Create a component on the configured Atlassian Statuspage page.
`statuspage.statuspage_update_component`	Write `write`	7	Update an existing component on the configured Atlassian Statuspage page.
`statuspage.statuspage_delete_component`	Write `write`	1	Delete a component from the configured Atlassian Statuspage page.