StatusCake MCP server
StatusCake in any MCP client, through Memtro: StatusCake does not publish this server. Memtro's StatusCake connector reads StatusCake through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
StatusCake monitoring: uptime checks with status and uptime, each check's downtime periods, alerts and recent results, SSL certificate checks, heartbeat and page-speed checks, and maintenance windows; can create, change, pause, resume and delete uptime checks, create, change and delete maintenance windows, and create heartbeat and SSL checks.
Reads
statuscake_list_uptime_checksStatusCake uptime checks: name, URL, type, status (up or down), uptime percentage, check rate, paused, tags.statuscake_get_uptime_checkOne StatusCake uptime check by id: everything in the list plus when it was last tested, timeout, confirmation servers…statuscake_uptime_check_historyFor one StatusCake uptime check, newest first: `periods` (up and down spells with start, end and duration — use for 'when was it down'), `alerts`…statuscake_list_ssl_checksStatusCake SSL certificate checks: URL, certificate status and score, valid from and until (expiry), issuer, and whether it is expired, broken…statuscake_list_heartbeat_checksStatusCake heartbeat checks (jobs that must check in): name, status, expected period, uptime, paused, tags.statuscake_list_pagespeed_checksStatusCake page-speed checks: name, URL, location, check rate, and the latest load time, page size, request count and whether it has an issue.statuscake_list_maintenance_windowsStatusCake maintenance windows (when alerting is suppressed): name, start and end, repeat interval, state (active, paused, pending), timezone…
Acts, when you ask
These change something in StatusCake. 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.
statuscake_create_uptime_checkCreate a StatusCake uptime check that starts testing the URL or host at once (unless `paused`).statuscake_update_uptime_checkChange a StatusCake uptime check: pause or resume it (`paused`), or change its name, URL, rate, tags, regions, contact groups or alert settings.statuscake_delete_uptime_checkPermanently delete a StatusCake uptime check, with its history, periods and alerts.statuscake_create_maintenance_windowCreate a StatusCake maintenance window.statuscake_update_maintenance_windowChange a StatusCake maintenance window: its name, times, timezone, repeat, or the checks and tags it covers (a list given replaces the whole list).statuscake_delete_maintenance_windowPermanently delete a StatusCake maintenance window.statuscake_create_heartbeat_checkCreate a StatusCake heartbeat check, which goes down when nothing pings it for `period_seconds`.statuscake_create_ssl_checkCreate a StatusCake SSL certificate check on an https URL.
Connect it
First connect StatusCake on Dashboard → Connections, then add Memtro to your client once. The StatusCake tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
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 StatusCake 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
- › When was the website last down, and for how long?
- › Which uptime checks are down right now?
- › Which SSL certificates expire in the next 30 days?
- › Did the nightly backup heartbeat check in last night?
- › Set a maintenance window for the API checks on Saturday from 22:00 to 23:00
Questions
- Is this an official StatusCake MCP server?
- No. It is Memtro's MCP server with Memtro's StatusCake connector behind it: the connector reads StatusCake through its API with the credentials you connect on Dashboard → Connections, and StatusCake 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 StatusCake?
- Only when you ask, and only what it has been granted: create an uptime check (counts against the plan's check quota; its contact groups are alerted when it fails); change an uptime check's settings, or pause or resume it; delete an uptime check and its history (permanent); create a maintenance window (silences alerts for the checks it covers); change a maintenance window; delete a maintenance window (permanent); create a heartbeat check (its push URL is not returned); create an SSL certificate check. 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.