OBSERVABILITY / Checkly
Checkly MCP Server
Checkly's hosted MCP server over Streamable HTTP: inspect check status and results, test sessions, RCA and result assets, trigger deployed checks, manage monitors and groups, environment variables and status-page incidents. OAuth is recommended; user and service API keys are the documented alternatives.
“The Checkly MCP Server lets MCP clients connect to Checkly over Streamable HTTP and use Checkly tools from your conversation.”
01 / THE REASONING
Why this made the selection.
- The publisher hosts the server itself for live account operations, and the docs draw an explicit boundary against the local CLI path — the MCP server is for reading and acting on deployed checks, not for authoring check code.
- Three documented auth modes with distinct blast radius — OAuth for interactive use, user API keys (cu_) for personal clients, service API keys (sv_) for non-interactive account-scoped identities — plus an X-Checkly-Account header for multi-account users.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Checkly MCP Server documentation: the endpoint is https://api.checklyhq.com/mcp over Streamable HTTP; the tool surface covers account context, synthetic and uptime monitors and groups (create, read, update, delete), check status and results, test sessions, result assets, Rocky AI root cause analyses, triggering deployed checks, environment variables and secrets, and status pages with incident management.
- Checkly setup guide: OAuth is recommended and avoids storing a long-lived credential; user API keys start with cu_ and use the user's permissions; service API keys start with sv_ and bind to a configured account and role; the X-Checkly-Account header selects the account in multi-account setups.
- Checkly changelog (June 25, 2026): the MCP Server is now available, giving agents OAuth-based access to inspect live monitoring data and help with incident workflows.
Our findings
- The publisher positions MCP, Skills and the CLI as complementary surfaces with a documented division of labour: MCP for live account data and remote actions, Skills plus the CLI for authoring and deploying check code.
- The server is hosted; no official server source repository exists, so repository and revision are null per the hosted-server precedent.
- Correction, 2026-10-13: the earlier record said secret values stay protected through the server. Neither cited page says so; the documentation says the server can manage account-level environment variables and secrets.
- Correction, 2026-10-13: the earlier configExample matched no printed block. It is now the setup guide’s VS Code .vscode/mcp.json block.
- OAuth supports only Checkly-approved clients; clients that rely on Dynamic Client Registration are rejected, and Cline is named as not supported for Checkly OAuth.
Not established by this review
- No Checkly account was connected and no check, RCA or status-page operation was executed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add https://api.checklyhq.com/mcp as a remote MCP server in the client.
- Authenticate via the client's OAuth flow, or send an Authorization header carrying a user (cu_) or service (sv_) API key.
- If you belong to multiple accounts, set the X-Checkly-Account header or name the account in the prompt.
Before you start
- A Checkly user account with access to the target account.
- An OAuth-capable client, or a client that can send custom HTTP headers for API-key authentication.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"servers": {
"checkly": {
"type": "http",
"url": "https://api.checklyhq.com/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://www.checklyhq.com/docs/ai/mcp-server
Supports: summary, upstreamDescription, descriptionSourceUrl, bestFor, limitations, whySelected, access, review
https://www.checklyhq.com/docs/ai/mcp-server/setup
Supports: configExample, install, access, compatibility, transports
https://feedback.checklyhq.com/changelog
Supports: summary, whySelected