Checkly MCP server

What the model can do

Checkly synthetic monitoring: checks and whether each is passing, failing or degraded now, raw results of the last hours with response times and locations, check groups, error groups, status pages and maintenance windows. Can run checks now, open, update and resolve status page incidents, archive an error group, schedule, change or delete a maintenance window, create a URL monitor and delete a check.

Reads

• checkly_list_checksChecks configured in Checkly: name, type (API, BROWSER, HEARTBEAT, TCP…), active or muted, how often it runs, from which locations, tags…
• checkly_check_statusesWhether each check is passing right now: failing, erroring or degraded, the longest and shortest recent run, the last location…
• checkly_check_resultsRaw results of one check over a window of at most six hours (default the last six): when each run started, response time, location…
• checkly_list_check_groupsCheck groups: name, active or muted, tags, locations and how many checks each holds.
• checkly_error_groupsThe distinct errors one check has failed with, as Checkly clusters them: the error message and when it was first and last seen.
• checkly_list_status_pagesCheckly status pages (v3, components-based): id, name, address and whether private.
• checkly_get_status_pageOne Checkly status page's components (id, name, service or group) and its incidents, most recently updated first (id, name, last status…
• checkly_list_maintenance_windowsCheckly maintenance windows: id, name, start and end, repeat, the tags they cover, whether they silence alerts or pause checks…

Acts, when you ask

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

• checkly_trigger_checksRuns Checkly checks now ("Schedule now"): the checks named by id, or every check (and group) carrying all the given tags.
• checkly_cancel_check_sessionCancels the in-progress runs of a Checkly check session (Playwright Check Suites only).
• checkly_open_status_page_incidentOpens an incident on a Checkly status page with its first update and the status of impacted components.
• checkly_post_status_page_incident_updatePosts an update to a Checkly status page incident (INVESTIGATING, IDENTIFIED, MONITORING, or RESOLVED, which closes it).
• checkly_update_status_page_incidentRenames a Checkly status page incident and sets the full list of impacted components (any component left out shows as operational).
• checkly_archive_error_groupArchives a Checkly error group, until its next occurrence or for ever, so it stops showing as a current error.
• checkly_create_maintenance_windowSchedules a Checkly maintenance window.
• checkly_update_maintenance_windowChanges a Checkly maintenance window; only the fields given change (Checkly's update is partial).
• checkly_delete_maintenance_windowPermanently deletes a Checkly maintenance window; alerts and checks it silenced or paused go back to normal.
• checkly_create_url_checkCreates a Checkly URL monitor that sends a GET to an address every so often from the chosen locations and alerts on failure under the account's alert…
• checkly_delete_checkPermanently deletes a Checkly check with all its status and results history; its alerts stop.

Connect it

First connect Checkly on Dashboard → Connections, then add Memtro to your client once. The Checkly 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 Checkly 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 Checkly checks are failing right now?
• › When did the login browser check start failing, and from which locations?
• › Which SSL certificates expire in the next 30 days?
• › Run the checkout checks again now
• › Open an incident on the status page saying payments are degraded and we are investigating

Questions

Is this an official Checkly MCP server?

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

Only when you ask, and only what it has been granted: run checks now, by id or by tag, using the run quota; cancel a running Playwright check session; open an incident on a status page (public); post an update to a status page incident, or resolve it (public); rename a status page incident or change its impacted components (public); archive an error group; schedule a maintenance window that silences alerts or pauses checks; change a maintenance window; delete a maintenance window; create a URL monitor; permanently delete a check and its history. 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