monitoring
Atlassian Statuspage MCP Gateway for AI Agents
Expose Atlassian Statuspage tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.
5 functions 3 read 2 write API key auth
Atlassian Statuspage MCP Gateway
Expose Atlassian Statuspage to MCP clients with `kosmokrator mcp:serve --integration=statuspage`.
If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash kosmokrator mcp:gateway:install --integration=statuspage --write=deny --json {
"mcpServers": {
"kosmokrator-statuspage": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=statuspage",
"--write=deny"
]
}
}
} Serve Manually
kosmokrator mcp:serve --integration=statuspage --write=deny MCP Tool Names
KosmoKrator exposes integration tools through the gateway with stable names:
| MCP tool | Source function | Type |
|---|---|---|
integration__statuspage__statuspage_list_incidents | statuspage.statuspage_list_incidents | Read read |
integration__statuspage__statuspage_create_incident | statuspage.statuspage_create_incident | Write write |
integration__statuspage__statuspage_update_incident | statuspage.statuspage_update_incident | Write write |
integration__statuspage__statuspage_list_components | statuspage.statuspage_list_components | Read read |
integration__statuspage__statuspage_get_current_user | statuspage.statuspage_get_current_user | Read read |
Write Access
Start with --write=deny for read-only MCP clients. Use --write=ask or
--write=allow only when the client and workspace are trusted.