Drumbeats MCP Server

Operate Drumbeats cron/uptime monitors, incidents, and HTTP/SSL/DNS checks from any AI client.

Documentation

Drumbeats MCP

CI npm License: Apache-2.0 drumbeats-io/mcp MCP server

The official Model Context Protocol server for Drumbeats — run your monitoring from any AI client. Create monitors, triage incidents, and run HTTP / SSL / DNS checks in plain language from Claude, Cursor, VS Code, or any MCP-capable tool.

What is Drumbeats?

Drumbeats is heartbeat and uptime monitoring for background jobs and services — cron jobs, queues, scheduled tasks, and HTTP endpoints. If a job stops checking in or a site goes down, Drumbeats alerts you. Create a free account at drumbeats.io.

Install

Add the server to your AI client and set one environment variable — your Drumbeats account API key:

{
  "mcpServers": {
    "drumbeats": {
      "command": "npx",
      "args": ["-y", "@drumbeats/mcp"],
      "env": { "DRUMBEATS_API_KEY": "dk_your_key" }
    }
  }
}
  1. Get a key — at drumbeats.ioAccount → API keys. An account-scoped key (dk_…) works across every project you own or belong to.
  2. Add the config — paste the block above into your client's MCP config and restart it.
  3. Ask"List my monitors."

Claude Desktop: prefer a one-click install — download the latest .mcpb bundle from the Releases page, double-click it, and paste your key when prompted.

Requires Node.js 22 when running via npx.

Tools

Sixteen tools over one shared layer. The HTTP / SSL / DNS diagnostics work with no account and no API key — point any client at the server and start checking.

Projects & monitors

ToolWhat it does
list_projectsList the projects your key can access (with notification channels and groups).
create_projectCreate a new project (account-scoped key with manage_projects).
update_projectUpdate a project's name or description (partial patch).
create_monitorCreate a monitor — cron, heartbeat, or HTTP uptime.
list_monitorsList a project's monitors with type, status, and schedule.
get_monitorFetch one monitor by id, with its full configuration.
update_monitorUpdate an existing monitor (partial patch).
pause_monitorPause a monitor (stops checks and alerts).
resume_monitorResume a paused monitor.

Observe & triage

ToolWhat it does
get_monitor_historyRecent pings, checks, and response times for a monitor.
get_uptime_summaryProject-wide uptime / SLA rollup across monitors.
list_incidentsList incidents (downtime and missed runs), filterable by status or monitor.
manage_incidentGet, acknowledge, or resolve an incident.

Diagnostics — no account required

ToolWhat it does
check_httpCheck a URL's reachability, status code, and response time.
check_sslInspect a TLS certificate — validity, expiry, and issuer.
check_dnsResolve a hostname and report its DNS records.

Example prompts

List all my monitors and their current status.
Create a cron monitor for my nightly backup that runs every day at 02:00 UTC.
What's my uptime this month?
Show me open incidents and acknowledge the most recent one.
Is https://example.com up right now?            # no account needed
Is the SSL certificate for example.com about to expire?   # no account needed

Try it with zero setup

The check_http, check_ssl, and check_dns tools need no Drumbeats account or API key. Add the server, leave DRUMBEATS_API_KEY unset, and ask "Is my site up?" before you sign up. When you're ready for continuous monitoring and alerts, create a free account.

Configuration

VariableRequiredDefaultDescription
DRUMBEATS_API_KEYFor the monitoring toolsAccount-scoped key (dk_…). Not needed for the diagnostics tools.
DRUMBEATS_API_BASE_URLNohttps://api.drumbeats.ioThe apex REST URL. The Drumbeats API is split across services by path prefix (/id, /beats, /alerts); the client appends the per-service prefix to this apex per request.
DRUMBEATS_ID_BASE_URLNo${apex}/idSelf-host override: full base URL for the id service.
DRUMBEATS_BEATS_BASE_URLNo${apex}/beatsSelf-host override: full base URL for the beats service.
DRUMBEATS_ALERTS_BASE_URLNo${apex}/alertsSelf-host override: full base URL for the alerts service.

Development

Requires the Node version in .nvmrc.

npm ci          # install dependencies
npm run build   # compile TypeScript to dist/
npm run lint    # Biome lint + format check
npm test        # run the test suite

See CONTRIBUTING.md for the contribution workflow and SECURITY.md for the security policy. This is a security product — please report vulnerabilities privately.

Links

License

Apache-2.0 © Lucky S Software. See NOTICE.


A product by Lucky S Software.