Instatus MCP server

What the model can do

Instatus status pages: pages and their overall status, incidents with their updates and on-call responders, components and their status, scheduled maintenance, notices, and uptime monitors with availability over a period; when you ask, can open, update, resolve, acknowledge and delete incidents, schedule, update and cancel maintenance, change or add components, post or remove notices, add or remove a subscriber, and pause, mute or resume a monitor.

Reads

• instatus_list_pagesThe status pages this key can see, with each page's id, overall status (UP, HASISSUES, SOMEPARTIALOUTAGE…) and public address.
• instatus_list_incidentsIncidents on a status page, newest first: name, status, impact, start and resolution times, the components affected and the latest update.
• instatus_get_incidentOne incident in full: every update with its message and status, the components and their status, and who was paged and has acknowledged…
• instatus_list_componentsThe components of a status page (Website, API, App…) with their current status, description, group and whether uptime is shown.
• instatus_list_maintenancesScheduled maintenance on a status page: name, status (NOTSTARTEDYET, INPROGRESS, COMPLETED), start, end or duration, components and the latest update.
• instatus_list_noticesThe notices (persistent banners) on a status page: title, message, whether subscribers were notified, created and updated times.
• instatus_list_monitorsUptime monitors for a status page: name, type, the address checked (without its query or credentials), status (UP, DOWN, DEGRADED, UNKNOWN)…
• instatus_monitor_uptimeA monitor's availability over a period: percentage of successful checks, failed checks, downtime, average response time, and a day-by-day breakdown.

Acts, when you ask

These change something in Instatus. 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.

• instatus_create_incidentOpens an incident on an Instatus status page.
• instatus_update_incidentChanges an Instatus incident's name, its components or their status; only the fields passed change.
• instatus_post_incident_updatePosts an update on an Instatus incident, shown publicly on the status page, with its new status; status RESOLVED resolves the incident.
• instatus_acknowledge_incidentAcknowledges an incident as the API key's user.
• instatus_delete_incidentPermanently deletes an Instatus incident and its updates from the status page and its history.
• instatus_schedule_maintenanceSchedules a maintenance window on an Instatus status page, shown publicly.
• instatus_post_maintenance_updatePosts an update on an Instatus maintenance, shown publicly, with its new status (INPROGRESS starts it, COMPLETED ends it).
• instatus_delete_maintenancePermanently deletes a scheduled maintenance from an Instatus status page, which is how a planned window is cancelled.
• instatus_update_componentChanges an Instatus component's status (shown publicly at once, without an incident or any notification), name…
• instatus_create_componentAdds a component to an Instatus status page, shown publicly.
• instatus_post_noticePosts a notice, a persistent banner, on an Instatus status page, shown publicly until deleted.
• instatus_delete_noticePermanently deletes a notice from an Instatus status page.
• instatus_add_subscriberSubscribes an email address to an Instatus status page, for all components or the ones named.
• instatus_remove_subscriberRemoves the subscriber with this exact email address from an Instatus status page; they stop receiving its notifications and are not told.
• instatus_set_monitor_statePauses, mutes or resumes an Instatus monitor.

Connect it

First connect Instatus on Dashboard → Connections, then add Memtro to your client once. The Instatus 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 Instatus 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

• › Which incidents are unresolved on our status page?
• › What is the status of each component right now?
• › What was the API monitor's uptime over the last 30 days?
• › Is any maintenance scheduled this week?
• › Post an update on the login incident saying a fix is rolling out.

Questions

Is this an official Instatus MCP server?

No. It is Memtro's MCP server with Memtro's Instatus connector behind it: the connector reads Instatus through its API with the credentials you connect on Dashboard → Connections, and Instatus 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 Instatus?

Only when you ask, and only what it has been granted: open an incident on a status page; rename an incident or change its components; post an incident update, including resolving it; acknowledge an incident as the key's user; delete an incident; schedule a maintenance; post a maintenance update; delete a maintenance; change a component's status, name or description; add a component to a status page; post a notice on a status page; delete a notice; subscribe an email address to a status page; remove a subscriber from a status page; pause, mute or resume a monitor. 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