Drumbeats MCP · setup

Connect Drumbeats to your AI client.

Add the official Drumbeats MCP server to Claude, Cursor, VS Code, or any MCP client. Connect the hosted server over OAuth in one command — or run it locally with an API key.

Connect the hosted serverLocal install

New to this? What is the Drumbeats MCP? →

From zero to first answer in three steps

Add the server, sign in, then just ask.

1

Add the server

One command points your client at the hosted URL — https://api.drumbeats.io/mcp. Pick your client →
2

Sign in

Your browser opens to authorize over OAuth — no API key to mint or paste. Approve once and you're connected.
3

Ask

Talk to your monitoring in plain language: "List my monitors" or "Is example.com up?"
Recommended

Connect the hosted server

Point your client at the remote URL and sign in through OAuth. Nothing to install, no API key to store.

Remote URL

https://api.drumbeats.io/mcp

Claude web & Desktop — add a connector

In Claude, open Settings → Connectors → Add custom connector, paste the remote URL above, and sign in when prompted.

Or add it from your terminal (Claude Code, or Claude Desktop via the CLI):

bash
claude mcp add --transport http drumbeats https://api.drumbeats.io/mcp

The first call opens your browser to authorize. Then ask it to list your monitors.

Fallback

Or run it locally

Run the server over stdio with an API key — good for offline setups and pinned versions. Requires Node.js 22 when running via npx.

1 · Mint an API key

An account-scoped key (dk_…) that works across every project you own. Mint your key →

Fastest: install the bundle

Download the latest .mcpb bundle, double-click it, and paste your key when prompted.

Download the bundle

Or add it manually to claude_desktop_config.json:

json
{
  "mcpServers": {
    "drumbeats": {
      "command": "npx",
      "args": ["-y", "@drumbeats/mcp"],
      "env": { "DRUMBEATS_API_KEY": "dk_your_key" }
    }
  }
}

Restart your client, then ask it to list your monitors.

16 tools, one shared layer

Everything your AI client needs to run and watch your monitoring.

Monitors & projects

  • list_projects

    List the projects your key can access, with channels and groups.

  • create_project

    Create a new project — needs a key with the manage_projects scope.

  • update_project

    Update a project's name or description with a partial patch.

  • create_monitor

    Create a monitor — cron, heartbeat, or HTTP uptime.

  • list_monitors

    List a project's monitors with type, status, and schedule.

  • get_monitor

    Fetch one monitor by id, with its full configuration.

  • update_monitor

    Update an existing monitor with a partial patch.

  • pause_monitor

    Pause a monitor — stops checks and alerts.

  • resume_monitor

    Resume a paused monitor.

Observe & triage

  • get_monitor_history

    Recent pings, checks, and response times for a monitor.

  • get_uptime_summary

    Project-wide uptime / SLA rollup across monitors.

  • list_incidents

    List incidents — downtime and missed runs — by status or monitor.

  • manage_incident

    Get, acknowledge, or resolve an incident.

Diagnostics

No API key
  • check_http

    Check a URL's reachability, status code, and response time.

  • check_ssl

    Inspect a TLS certificate — validity, expiry, and issuer.

  • check_dns

    Resolve a hostname and report its DNS records.

Things to ask it

Copy a prompt and paste it into your client.

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?

Is the SSL certificate for example.com about to expire?

Works with no account

The check_http, check_ssl, and check_dns tools need no Drumbeats account and no API key. Point any client at the local server and start checking before you sign up — just omit the env entirely:

json
{
  "mcpServers": {
    "drumbeats": {
      "command": "npx",
      "args": ["-y", "@drumbeats/mcp"]
    }
  }
}

Is https://example.com up right now?

Is the SSL certificate for example.com about to expire?

Then create a free account →

Tell your coding agent

Paste this into your AGENTS.md (or CLAUDE.md) so your coding agent knows the Drumbeats MCP is available.

markdown
## Monitoring (Drumbeats MCP)

The Drumbeats MCP server is available. Use it for uptime, cron, and
heartbeat monitoring of this project.

- Find the project with `list_projects` (or `create_project` /
  `update_project` with a `manage_projects`-scoped key), then
  `create_monitor` / `list_monitors` to set up and review monitors.
- Triage failures with `list_incidents` and `manage_incident`.
- Ad-hoc `check_http` / `check_ssl` / `check_dns` need no API key.

The full source is on GitHub.

What is the Drumbeats MCP?