Cachet MCP server

What the model can do

Cachet (self-hosted status page, v3): overall status, incidents with status, message and updates, components and groups with their status, scheduled maintenance, and metrics with their points; can create, update and delete incidents and post incident updates, create, update and delete components and set their status, schedule, update and delete maintenance, record metric points, and add or remove subscribers.

Reads

• cachet_get_statusThe overall status of the Cachet status page (operational, partial outage, major outage or under maintenance) and its message.
• cachet_list_incidentsIncidents on the Cachet status page: name, status, message, visibility and when it occurred, newest first by default.
• cachet_get_incidentOne Cachet incident with its updates (status and message, in order) and the components it affects.
• cachet_list_componentsComponents on the Cachet status page and their current status (operational, performance issues, partial or major outage, under maintenance).
• cachet_list_component_groupsComponent groups on the Cachet status page, with the components in each.
• cachet_list_schedulesScheduled maintenance on the Cachet status page: name, status (upcoming, in progress, complete), message, and when it is scheduled and completed.
• cachet_list_metricsMetrics on the Cachet status page: name, suffix, description, how points combine (sum or average) and visibility.
• cachet_get_metric_pointsThe most recent points of one Cachet metric: value, calculated value and when it was recorded.

Acts, when you ask

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

• cachet_create_incidentCreate an incident on the Cachet status page.
• cachet_update_incidentChange a Cachet incident's name, message, status, visibility or pinning; only the fields given change.
• cachet_add_incident_updatePost an update to a Cachet incident, with its new status (fixed resolves it) and a message, shown on the public status page at once.
• cachet_delete_incidentPermanently delete a Cachet incident and its updates from the status page (cannot be undone; resolving it with status fixed keeps the history).
• cachet_create_componentAdd a component (a service shown on the status page) to Cachet, with its status, link and group.
• cachet_update_componentChange a Cachet component: its public status (operational, performance issues, partial or major outage, under maintenance), name, link…
• cachet_delete_componentPermanently delete a component from the Cachet status page (cannot be undone).
• cachet_create_scheduleSchedule maintenance on the Cachet status page, shown publicly, with the components it affects.
• cachet_update_scheduleChange scheduled maintenance on the Cachet status page: name, message, start or end time, or affected components.
• cachet_add_schedule_updatePost an update to scheduled maintenance on the Cachet status page; completed_at marks it complete.
• cachet_delete_schedulePermanently delete scheduled maintenance from the Cachet status page (cannot be undone).
• cachet_add_metric_pointRecord a value on a Cachet metric (shown on the status page's chart if the metric is visible), now or at a given time.
• cachet_add_subscriberSubscribe an email address to the Cachet status page's notifications, for every component (global) or the ones named.
• cachet_delete_subscriberPermanently remove a subscriber from the Cachet status page, named by id or by their exact email address, so they stop receiving notifications.

Connect it

First connect Cachet on Dashboard → Connections, then add Memtro to your client once. The Cachet 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 Cachet 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 the status page right now?
• › What updates were posted on last week's API incident?
• › What maintenance is scheduled for this month?
• › Which components are in the payments group?
• › Post an update on the login incident saying a fix is rolling out.

Questions

Is this an official Cachet MCP server?

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

Only when you ask, and only what it has been granted: create an incident on the status page (can notify subscribers); change an incident's name, message, status or visibility; post an update to an incident; delete an incident (permanent); add a component to the status page; change a component, including its public status; delete a component (permanent); schedule maintenance (can notify subscribers); change scheduled maintenance; post an update to scheduled maintenance, or mark it complete; delete scheduled maintenance (permanent); record a metric point; subscribe an email address to status updates; remove a subscriber. 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