MCP: Axiom
by Axiom
Axiom's official MCP server — query event data with APL, read dataset schemas, and create or edit dashboards, monitors and notifiers from an agent.
Checkly's hosted MCP server gives an agent read access to your synthetic monitoring account — check health, failing results, test sessions, Rocky AI root-cause analyses, incidents and status pages — over streamable HTTP with OAuth.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Checkly runs Playwright-based synthetic checks against production and tells you when a user journey breaks. The Checkly MCP Server is the first-party way to bring that signal into an agent session: instead of pasting a failing check's output into a chat, the agent queries the account directly while it is looking at the code.
There is nothing to install. The server is Checkly-operated at https://api.checklyhq.com/mcp, speaks streamable HTTP, and is reached the same way from any client that supports the transport:
claude mcp add --transport http checkly https://api.checklyhq.com/mcpOAuth is the recommended authentication path and covers Checkly-approved clients. Where OAuth is not an option — or where a workflow needs a stable service identity — a user or service API key works through an Authorization: Bearer <key> header, with X-Checkly-Account selecting which account to read when a key spans more than one.
The tool surface follows the product: account membership, plan and feature entitlements; check state (passing, failing, muted, deactivated); check results and test-session data; result assets and normalised manifests; status pages and incidents; and account environment variables. It can start or read a Rocky AI root-cause analysis, and it can trigger an existing check on demand — useful for confirming that a fix actually cleared the failure rather than guessing.
The practical pattern is incident work. A check goes red, and the same session that holds your diff can pull the failing result, read the RCA, and re-run the check after the fix — no tab switching, no copy-pasting logs, and no separate deploy to observe. For teams already running Checkly's monitoring-as-code workflow, it closes the loop between the agent that wrote the change and the monitors that judge it.
The scopes are granular and listed explicitly in Checkly's setup docs — reads for checks, results, RCA, test sessions, assets, incidents, status pages and usage, plus writes for checks, incidents, environment variables and account invites. Grant the narrow set your workflow needs; a monitoring account holds environment variables and secrets alongside the check data.
by Axiom
Axiom's official MCP server — query event data with APL, read dataset schemas, and create or edit dashboards, monitors and notifiers from an agent.
by Memfault (Nordic Semiconductor)
Remote MCP server for Memfault (Nordic Semiconductor) exposing 18 read-only tools over device fleet telemetry — device vitals, timeseries, crash issues, traces, metrics and software versions.
by Sentry
Sentry's official MCP server — investigate errors and issues, inspect events, and use Seer for root-cause analysis.
by incident.io
incident.io's official hosted MCP server — reach incidents, alerts, on-call schedules, the catalog and workflows from Claude, Cursor or any MCP client over OAuth.