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 MCP Integration for LangChain

Connect Atlassian Statuspage to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

5 functions 3 read 2 write API key auth

Submit Atlassian Statuspage feedback View package source

Connect Atlassian Statuspage to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Atlassian Statuspage MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-statuspage": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=statuspage",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=statuspage --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Atlassian Statuspage instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Atlassian Statuspage Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Atlassian Statuspage integration catalog.

MCP tool	Source function	Type	Description
`integration__statuspage__statuspage_list_incidents`	`statuspage.statuspage_list_incidents`	Read	List all incidents for your Atlassian Statuspage. Returns scheduled, ongoing, and resolved incidents with their current status and impact.
`integration__statuspage__statuspage_create_incident`	`statuspage.statuspage_create_incident`	Write	Create a new incident on your Atlassian Statuspage. Specify the incident name, status, impact level, and an optional body describing the issue.
`integration__statuspage__statuspage_update_incident`	`statuspage.statuspage_update_incident`	Write	Update an existing incident on your Atlassian Statuspage. Change the status, add updates to the body, or modify impact level.
`integration__statuspage__statuspage_list_components`	`statuspage.statuspage_list_components`	Read	List all components on your Atlassian Statuspage. Returns component names, current status, and group information.
`integration__statuspage__statuspage_get_current_user`	`statuspage.statuspage_get_current_user`	Read	Get the currently authenticated Atlassian Statuspage user. Useful for verifying API credentials and checking user permissions.

Related Atlassian Statuspage Pages

Atlassian Statuspage CLIUse direct JSON commands instead of MCP discovery. Atlassian Statuspage MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.