API and MCP operation map
All REST paths below are relative to /api/v1. MCP exposes the same
operation names as tools. Primary scopes do not replace association scopes
or current account permissions.
| MCP tool | REST method and path | Primary scope | Reference |
|---|---|---|---|
get_account_capabilities |
GET /capabilities |
account:read |
Capabilities |
list_checks |
GET /checks |
checks:read |
Checks |
get_check |
GET /checks/:id |
checks:read |
Checks |
create_check |
POST /checks |
checks:create |
Checks |
update_check |
PATCH /checks/:id |
checks:update |
Checks |
get_check_ping_urls |
GET /checks/:id/ping_urls |
checks:ping_urls |
Heartbeats |
get_check_history |
GET /checks/:id/history |
checks:history |
Diagnostics |
list_check_runs |
GET /checks/:id/runs |
checks:history |
Diagnostics |
get_check_metrics |
GET /checks/:id/metrics |
checks:history |
Diagnostics |
get_check_uptime |
GET /checks/:id/uptime |
checks:history |
Diagnostics |
list_notification_groups |
GET /notification_groups |
notification_groups:read |
Groups |
list_dashboards |
GET /dashboards |
dashboards:read |
Dashboards |
get_dashboard |
GET /dashboards/:id |
dashboards:read |
Dashboards |
create_dashboard |
POST /dashboards |
dashboards:create |
Dashboards |
update_dashboard |
PATCH /dashboards/:id |
dashboards:update |
Dashboards |
attach_check_to_dashboard |
PUT /dashboards/:dashboard_id/checks/:check_id |
dashboards:assign |
Dashboards |
detach_check_from_dashboard |
DELETE /dashboards/:dashboard_id/checks/:check_id |
dashboards:assign |
Dashboards |
reorder_dashboard_checks |
PUT /dashboards/:dashboard_id/check_order |
dashboards:assign |
Dashboards |
list_incidents |
GET /incidents |
incidents:read |
Incidents |
get_incident |
GET /incidents/:id |
incidents:read |
Incidents |
The separate /ping/<location-token> ingestion interface is not an
automation-grant REST operation or MCP tool.
No public automation operation deletes a check/dashboard, changes check kind, pauses/resumes a check, writes an incident update, creates notification groups/channels, edits rosters, publishes a status page or manages billing. Use the appropriate signed-in UI and role for those customer actions.