API and MCP

Ask your AI assistant what is down.

Heedery has a REST API and an MCP server over the same workspace. Connect Claude, Cursor or VS Code and ask in plain words, or call the API from a script or CI.

MCP · in your AI assistant
01 — What you can do

Six tools that read, seven that write.

Each MCP tool calls the same code as its REST endpoint, so both follow the same plan, scope and rate limits.

Read

From Pro
  • whats_downThe whole workspace right now: what is up, down or paused, and since when
  • list_monitorsMonitors with their state and last check, filtered or searched
  • get_monitorOne monitor in full, with its certificate and domain expiry
  • get_metricsUptime and response times per day, for up to 90 days
  • list_incidentsIncidents, newest first, open or resolved
  • get_incidentAn incident’s timeline and what the failed check saw

Write

From Team
  • create_monitorAdd a monitor, within the plan’s limits
  • pause_monitorStop a monitor’s checks and alerts until it is resumed
  • resume_monitorStart its checks again
  • acknowledge_incidentMark an incident as handled, which stops repeat alerts and escalation
  • comment_on_incidentAdd an internal note to an incident’s timeline
  • start_maintenanceOpen a maintenance window now, for a number of minutes
  • end_maintenanceEnd a running window early
REST · which monitors are down
curl https://heedery.com/api/v1/monitors?status=down \
  -H "Authorization: Bearer hda_…"
MCP · add the server to Claude Code
claude mcp add --transport http heedery \
  https://heedery.com/api/mcp

The REST API also changes and deletes monitors, schedules maintenance ahead of time and reports deploys. The MCP server has no tool that deletes anything.

02 — How it starts

Sign in, or make a token.

  1. Step 1

    Connect

    Claude, Cursor and VS Code take the server’s address and sign in with your Heedery account in the browser. Scripts and CI use an API token from Settings → Integrations → API.

    https://heedery.com/api/mcp
  2. Step 2

    Pick read or write

    You choose the workspace and the scope when you connect, or the scope when you create a token. A read connection is given the reading tools only; the others are not listed to the assistant.

  3. Step 3

    Ask

    Try “what is down right now?” or “put the shop in maintenance for an hour”. The assistant picks the tool and the answer comes from the live workspace.

03 — The plan

Read from Pro, write from Team.

The limits are per token and per minute, with reads and writes counted apart. An MCP tool call counts like an API request.

Compare every plan
  • StarterNo API accessFree
  • ProRead only, 120 reads a minute$14 a month
  • TeamRead and write, 300 reads and 60 writes a minute$39 a month
  • AgencyRead and write, 600 reads and 120 writes a minute$99 a month
  • EnterpriseRead and write, 600 reads and 120 writes a minuteFrom $250 a month

Monthly prices in USD, excluding VAT. Yearly billing costs less; see the pricing page.

04 — Questions

Before you sign up.

Something else? Write to us.

You decide how far it goes: a connection made with the read scope cannot change anything. With write, every change is recorded in the workspace’s audit log under the connection’s name, and the server tells the assistant to confirm with you before it uses a write tool. The MCP server has no tool that deletes anything, and you can revoke a connection under Settings → Integrations → API.

Connect it to your monitors.

Start on the free plan and add your sites. The API opens when the workspace moves to Pro.

Start for free