Statuspage MCP server

What the model can do

Atlassian Statuspage: your status pages, incidents and scheduled maintenance with their status, impact, affected components and updates, and each component's current status. Can open, update, resolve or delete incidents, schedule maintenance, set component status, add or delete components, correct updates, draft and publish postmortems and save incident templates.

Reads

• statuspage_list_pagesThe Statuspage pages this connection can see, with their ids (needed by the other tools when there is more than one) and public addresses.
• statuspage_list_incidentsIncidents on a status page, newest first: name, status, impact, affected components, latest update and link.
• statuspage_get_incidentOne incident in full: every update posted (newest first), affected components, timings and the postmortem.
• statuspage_list_componentsComponents on a status page and their current status (operational, degraded_performance, partial_outage, major_outage, under_maintenance).

Acts, when you ask

These change something in Statuspage. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• statuspage_create_incidentOpen a live incident on a status page: name, status, a first update message, impact and the affected components with the status to set each to.
• statuspage_update_incidentChange an incident on the public status page: post a new update message, move its status (resolved closes it…
• statuspage_schedule_maintenanceSchedule a maintenance window on a status page, from start to end (ISO 8601 with an offset), with a message and the components affected.
• statuspage_delete_incidentDelete an incident or maintenance window and all its updates from the status page.
• statuspage_edit_incident_updateCorrect the text or display time of an update already posted on an incident (ids from statuspage_get_incident).
• statuspage_update_componentSet a component's status on the public status page (operational, degraded_performance, partial_outage, major_outage, under_maintenance)…
• statuspage_create_componentAdd a component to a status page, shown publicly (status operational unless given), optionally in a component group.
• statuspage_delete_componentDelete a component from a status page.
• statuspage_write_postmortemWrite an incident's draft postmortem, replacing any draft already there.
• statuspage_publish_postmortemPublish an incident's draft postmortem to the public status page.
• statuspage_create_incident_templateSave a reusable incident template on a status page (internal, publishes nothing): a template name, the incident title and message…

Connect it

First connect Statuspage on Dashboard → Connections, then add Memtro to your client once. The Statuspage tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Statuspage connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Is anything down on our status page right now?
• › What did we tell customers during last Tuesday's outage?
• › Is any maintenance scheduled for this week?
• › Open an incident for degraded API performance and notify subscribers
• › Resolve the login incident with an update that the fix is deployed

Questions

Is this an official Statuspage MCP server?

No. It is Memtro's MCP server with Memtro's Statuspage connector behind it: the connector reads Statuspage through its API with the credentials you connect on Dashboard → Connections, and Statuspage publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Statuspage?

Only when you ask, and only what it has been granted: open an incident on a status page, optionally notifying subscribers; update an incident: post an update, change its status (resolve it), impact or affected components; schedule a maintenance window; delete an incident from the page, permanently; correct the text or time of an update already posted; set a component's status, or rename or redescribe it; add a component to a page; delete a component, permanently; write an incident's draft postmortem, or publish it to the page; save an incident template. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server