OAuth is the recommended way to connect. The OAuth flow only supports Checkly-approved clients listed in setup. User and service API keys are available for clients that can send custom headers when OAuth is unavailable or a workflow needs a stable service identity.
What you can do
- Inspect account membership, plan, and feature entitlements.
- Create,read update and delete synthetic & uptime monitors and groups.
- 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 you begin
Before you begin
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 OAuth MCP client, or an MCP client that can send custom HTTP headers for API-key authentication.
Prompt
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
Prompt
Prompt
Prompt
Prompt
Prompt
Prompt