S
Statuspage MCP
44
Stack Score
Editorial pick✓ Verified workingMCP server
Statuspage MCP
Atlassian Statuspage incident + component ops.
Best for
Best for SRE + ops teams running public status pages.
At a glance
- Pricing
- open-source
- Setup time
- 20 minutes
- Learning curve
- easy
- Last verified
- 5/26/2026
What we love
- ✓Atlassian-maintained
- ✓Wide industry use
- ✓Strong incident-comm features
Where it falls short
- −Atlassian Statuspage plan required
- −Pricing per page
- −Best for public-status pages
Pricing
✓ Pricing verified Jun 14, 20261 tier
Open-source
$0
perpetual
- ✓MIT
Overview
MCP server for Atlassian Statuspage — incident + component + subscriber + metric ops. Public status page management exposed to Claude.
Key features
- ●Incident CRUD
- ●Component status
- ●Subscriber mgmt
- ●Metric publish
- ●API token auth
Best use cases
Public status ops
Let Claude publish + update incidents on public status page during outages.
Component status sync
Sync component status from monitoring tools via Claude.
Integrations
Similar tools
See all automation tools →One AI Stack pick every week.
The tool we’d pay for this week, why we’d pay for it, and what we’d skip. No promo spam.