Cronitor MCP server

What the model can do

Cronitor monitoring: cron jobs, heartbeats, checks and sites with their state, schedule and latest event, recent runs of a job, issues (incidents) by state and severity, and status pages; can open, change, assign, resolve and delete internal issues, and pause, resume, create, clone and delete monitors.

Reads

• cronitor_list_monitorsCronitor monitors: key, name, type (job, heartbeat, check, site), state (passing, failing, paused), schedule, latest event and issue…
• cronitor_get_monitorOne Cronitor monitor by key, with its recent runs (start, end, duration, outcome) where Cronitor records them.
• cronitor_list_issuesCronitor issues (incidents), newest first: name, severity, state, start, end and duration, monitors affected, alert count, whether on a status page…
• cronitor_get_issueOne Cronitor issue by its 16-character key, with its updates in order.
• cronitor_list_status_pagesCronitor status pages: name, current status, hosted subdomain or custom domain, whether public or private, and component count.

Acts, when you ask

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

• cronitor_create_issueOpen an internal issue in Cronitor, with a name and optionally a severity (Cronitor defaults to outage).
• cronitor_update_issueChange a Cronitor issue: its name, severity, state (resolved closes it) or the team member it is assigned to.
• cronitor_bulk_update_issuesChange the state of (for example resolve), or assign, up to 50 Cronitor issues named by key, in one call.
• cronitor_delete_issuePermanently delete a Cronitor issue and its updates.
• cronitor_pause_monitorPause a Cronitor monitor for `hours`, or until resumed if hours is left out.
• cronitor_resume_monitorResume a paused Cronitor monitor, so it alerts again on failure.
• cronitor_create_monitorCreate a Cronitor job (cron schedule) or heartbeat monitor.
• cronitor_clone_monitorCopy a Cronitor monitor.
• cronitor_delete_monitorPermanently delete a Cronitor monitor with its history.

Connect it

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

• › Did the nightly backup job run last night?
• › Which monitors are failing right now?
• › What issues did we have this week, and how long did each last?
• › Is the public status page showing everything as operational?
• › Pause alerts on the reporting job for two hours while we migrate it

Questions

Is this an official Cronitor MCP server?

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

Only when you ask, and only what it has been granted: open an internal issue (no update posted, not on any status page); change an issue's name, severity, state or assignee (no update posted, so subscribers are not notified); change the state of, or assign, several issues named by key; delete an issue (permanent); pause a monitor's alerts, for a number of hours or until resumed; resume a paused monitor; create a job or heartbeat monitor (its notification lists are alerted when it fails); clone a monitor (the copy keeps the original's notification lists); delete a monitor and its history (permanent). 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