Skip to main content
The Checkly MCP Server lets supported AI clients connect to Checkly over Streamable HTTP and use Checkly tools from your conversation. Use the production MCP endpoint in your client: 
https://api.checklyhq.com/mcp
The Checkly MCP Server only supports Checkly-approved clients that use OAuth Client ID Metadata Documents (CIMD). Clients that use Dynamic Client Registration (DCR) are rejected. See setup requirements for supported clients and details.
Use it when your agent needs live Checkly account context, check status, check results, test sessions, root cause analyses, result assets, status pages, incidents, account environment variables, or when it needs to trigger existing checks.
Use Checkly Skills and the Checkly CLI when your agent needs to create, edit, test, bundle, or deploy check code. The MCP server runs remotely and cannot access your local filesystem.

​
What you can do

  • Inspect account membership, plan, and feature entitlements.
  • Check which checks are passing, failing, muted, or deactivated.
  • Read compact check results and test-session results.
  • Fetch normalized result asset manifests and bounded text assets.
  • Start or read Rocky AI root cause analyses.
  • Trigger existing deployed checks on demand.
  • Manage account-level environment variables and secrets.
  • Read status pages and manage status page incidents.

​
Quick start

Before connecting an MCP client, ensure you have:
  • A Checkly user account.
  • Access to the Checkly account you want the MCP client to use.
  • A supported MCP client.
Add the Checkly MCP endpoint to your client, complete the OAuth flow, then ask your client to verify the connection:
Prompt
Use Checkly to show which accounts I can access.
If you belong to more than one Checkly account, tell your client which account to use in your prompt. To always use the same account, set the X-Checkly-Account header when your client supports custom MCP headers. See Set up the MCP server for client configuration examples.

​
Example prompts

Basic prompts:
Prompt
Show me the current status of my Checkly checks.
Prompt
List open status page incidents.
Prompt
What features are available on my current Checkly plan?
Advanced prompts:
Prompt
Investigate the latest failed result for the checkout API check. If there is an error group, check whether an RCA already exists before triggering a new one.
Prompt
Trigger the checks tagged production-smoke, then follow the test session until results are available.
Prompt
Create a major status page incident for the API outage, but do not notify subscribers until I confirm the message.

​
MCP, Skills, and CLI

MCP, Checkly Skills, and the Checkly CLI are complementary. The CLI can also read live Checkly data and remains the most capable path for scripted workflows and local Monitoring as Code projects. Use the MCP Server when you want a quick, OAuth-based connection from a supported client without setting up the Checkly CLI in that environment. Use Checkly Skills with the CLI when your agent needs to create, edit, test, or deploy code from your local project.
Use caseRecommended path
Ask quick, ad hoc questions from a supported clientMCP Server
Inspect live Checkly data without local CLI setupMCP Server
Trigger existing deployed checks from chatMCP Server or Checkly CLI
Create or edit check codeCheckly Skills with the Checkly CLI
Test, deploy, or automate local Monitoring as Code projectsCheckly CLI
Add reusable Checkly best practices to an agentCheckly Skills

​
Learn more