MCP.so
Sign In

Drumbeats MCP Server

@drumbeats-io

Basic information

Category

Databases

Transports

stdio

Author

drumbeats-io

Submitted by

Samed Kahyaoglu

About Drumbeats MCP Server

Operate Drumbeats monitoring from any AI client — create cron/heartbeat and uptime monitors, triage incidents, and run HTTP/SSL/DNS diagnostics (no account needed for diagnostics).

Drumbeats MCP Server config

Add this server to your MCP-compatible client using the configuration below.

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

Drumbeats MCP Server tools

14

List all Drumbeats projects the configured account API key can access. Returns each project id, name, plan, and basic metadata — use it to find the target project id before creating or querying monitors. Pass include=["channels","groups"] to also return each project's notification channels and groups, whose ids are needed to wire alerts when creating a monitor.

Create a Drumbeats monitor. One tool for all four types, chosen via "type": - JOB_CRON: a job that should run on a cron schedule (schedule = cron expression). - JOB_BASIC: a job expected on a fixed interval (schedule = interval, e.g. "5m"). - JOB_HEARTBEAT: a passive endpoint your job pings (schedule = expected interval). - UPTIME_HTTP: Drumbeats polls a URL (schedule = poll interval; requires uptime_url). All uptime_* fields are only valid when type is UPTIME_HTTP. Wire alerts at create time with notification_channel_ids / notification_group_ids (UUIDs discoverable via list_projects include=channels,groups). Notification channel types: EMAIL, SLACK, TELEGRAM, DISCORD, WEBHOOK, PAGERDUTY, SMS, PUSH.

List all monitors in a Drumbeats project (jobs and uptime checks), with their type, status, and schedule metadata. Requires a project_id from list_projects. Use it to find a monitor id before fetching details, history, or incidents.

Get a single Drumbeats monitor by id, including its type, status, schedule, and alerting metadata.

Update an existing Drumbeats monitor. Provide monitor_id plus only the fields to change. Set status to PAUSED or UP to pause/resume (or use pause_monitor / resume_monitor). The uptime_* fields apply to UPTIME_HTTP monitors.

Pause a monitor by id. It stops running checks and sending alerts until resumed.

Resume a paused monitor by id.

Fetch a monitor's recent history. One tool with a "kind" argument: pings | warnings | checks | response_times. Defaults to pings. Use it to answer "what happened with this monitor lately?".

Get the project-level uptime / SLA summary across all of a project's uptime monitors: overall uptime percentage plus per-monitor uptime, check counts, and response times over a look-back window. The answer to "what is my uptime this month?".

List incidents for a Drumbeats project (downtime / missed-run events), newest first and paginated. Requires a project_id from list_projects. Filter by status (OPEN, ACKNOWLEDGED, RESOLVED) or a single monitor.

Triage a Drumbeats incident: get its details, acknowledge it, or resolve it. One tool with an "action" argument.

Check whether an http(s) URL is reachable and report its status code and response time. Works with no Drumbeats account or API key — handy for a quick "is this site up?" before signing up.

Inspect a host's TLS/SSL certificate — validity, expiry date, and issuer. Works with no Drumbeats account or API key — useful for "is my SSL certificate about to expire?".

Resolve a hostname and report its DNS records (what the domain points to). Works with no Drumbeats account or API key — useful for "what does this domain resolve to?".

Overview

What is Drumbeats MCP?

The official MCP server for Drumbeats, a monitoring service for cron jobs, background workers and websites. When a job misses its schedule, reports a failure or a site stops answering, Drumbeats opens an incident and alerts you. The server gives Claude, Cursor, VS Code and other MCP clients 19 tools to work with your account.

How to use Drumbeats MCP

Hosted, no install: add https://api.drumbeats.io/mcp to your client and sign in with your Drumbeats account when it asks. In Claude Code: claude mcp add --transport http drumbeats https://api.drumbeats.io/mcp.

Local, with an API key: run npx -y @drumbeats/mcp with DRUMBEATS_API_KEY set (create a key at drumbeats.io/account/api-keys). Needs Node.js 22. A Claude Desktop bundle (.mcpb) is attached to every GitHub release.

Key features of Drumbeats MCP

  • Create, list, update, pause and resume cron, heartbeat and HTTP uptime monitors
  • Report job runs: start, success, failure
  • Read monitor history, uptime summaries and incidents; acknowledge or resolve incidents
  • Check a website, a TLS certificate or a DNS name without an account
  • Hosted (OAuth) or local (API key); every tool states the permission it needs

Use cases of Drumbeats MCP

  • "List my monitors and tell me which ones are down."
  • "Create a cron monitor for my nightly backup, every day at 02:00 UTC."
  • "What was my uptime over the last 30 days?"
  • "Show open incidents and acknowledge the newest one."
  • "Is https://example.com up right now? When does its certificate expire?"

Frequently asked questions

1

Do I need an API key?

Not for the hosted server, which uses OAuth. For local use set `DRUMBEATS_API_KEY`, or leave it out to use only the three checks.

2

What transports are supported?

Streamable HTTP (hosted) and stdio (local, via npm).

3

Is the server open source?

Yes. Apache-2.0, source at github.com/drumbeats-io/mcp.

Comments

More Databases MCP servers