AgentPhone
Give an AI agent its own US or Canada number to call and text.
Read Checkly checks, results and root-cause analyses in Claude; trigger runs, post status incidents, invite members.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Checkly MCP server is Checkly's official connector for synthetic monitoring. It lets Claude read checks, results, test sessions, root-cause analyses and status pages, and act: trigger checks, start analyses, manage environment variables, post status-page incidents and invite members. Anthropic lists 32 tools; Checkly documents 48. Every action needs both a session scope and an account role.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Because each tool needs a matching session permission and your Checkly role must allow the action. Checkly hides a tool from the tool list when the session lacks its permission, and rejects the call when the role is insufficient. The invite tool is also unavailable to API-key sessions. Call whoami to see which account and role the session is using, then reconnect with the permissions you need.
Checkly supports OAuth only for clients it has approved, and it rejects Dynamic Client Registration. Its approved list includes Claude Desktop, Claude Code, Cursor, VS Code and ChatGPT; Checkly names Cline, Windsurf and Codex OAuth as unsupported. If your client can send custom headers, connect with a current user key or service key in an Authorization Bearer header instead of OAuth.
Name the account in your prompt, or pin it with the X-Checkly-Account header if your client supports custom MCP headers. Checkly explains that OAuth sessions and user keys can reach several accounts, so tools may ask which one you mean. A service key is already scoped to a single account, so either remove the header or set it to that key's account.
initialize probe of https://api.checklyhq.com/mcp — HTTP 401 authentication challenge whose scope= lists 19 checkly: permissions, with resource_metadata at https://api.checklyhq.com/.well-known/oauth-protected-resource/mcp; the descriptor lists the same 19 and the authorization server https://auth.checklyhq.com/ (2026-11-18) · retrieved 2026-11-18anthropic-directory-2026-11-17.json) · retrieved 2026-11-17Connect Checkly once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.