Drumbeats Io

io.github.drumbeats-ioPublished by GitHub account drumbeats-iov0.5.2Updated Oct 29, 2026

Manage Drumbeats cron, heartbeat and uptime monitors, report job runs and handle incidents.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Official Drumbeats MCP server for creating and managing cron, heartbeat and uptime monitors, reporting job runs, and handling incidents.

What you can do
  • List, create and update projects and monitors, and pause or resume monitors
  • Report job starts, successes and failures with optional run id, message and payload
  • Read monitor history, uptime summaries and incidents, and acknowledge or resolve incidents
  • Check a URL's HTTP status, TLS certificate and DNS records without an account
When to use it
Useful when you want an assistant to set up or inspect Drumbeats monitoring for cron jobs, background workers and websites, report job outcomes from an agent, or triage open incidents. The three check tools are handy for quick ad-hoc site, certificate and DNS lookups even without an account.
Requirements
Either the hosted endpoint with OAuth sign-in, or the npm package run locally with npx, which needs Node.js 22. The local route needs a Drumbeats API key in DRUMBEATS_API_KEY (account-wide or limited to one project); the three check tools work without a key. Optional variables set the API timeout and base URL.
Before you install
The API key grants access to every project you own or belong to unless you use a project-scoped key, so keep it out of shared configs. Tools can create and change projects and monitors, pause checks, report job runs and acknowledge or resolve incidents, which affects alerting. The hosted server sends your account data to Drumbeats over the network.

Installation

In SourceWeft

  1. Open Drumbeats Io in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.drumbeats-io%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "drumbeats-io": {
      "type": "http",
      "url": "https://api.drumbeats.io/mcp"
    }
  }
}

README

[Drumbeats MCP: cron, heartbeat and uptime monitoring from your AI assistant]

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

Drumbeats watches cron jobs, background workers and websites. When a job misses its schedule, reports a failure or a site stops answering, it opens an incident and alerts you.

This is the official Model Context Protocol server for Drumbeats. It lets Claude, Cursor, VS Code and other MCP clients work with your account: create monitors, read their history, report job runs and handle incidents. Three of its tools check a website, a certificate or a DNS name and work without an account.

Connect

There are two ways to run it. Both give you the same 19 tools.

Hosted server

Add https://api.drumbeats.io/mcp to your client and sign in with your Drumbeats account when it asks. Nothing to install and no API key to store.

Claude (web, Desktop and Claude Code)

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

In Claude Code:

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

Add this to .cursor/mcp.json in your project, or to the global config, and approve the sign-in on first connect:

json
{  "mcpServers": {    "drumbeats": {      "url": "https://api.drumbeats.io/mcp"    }  }}
VS Code

Add this to .vscode/mcp.json in your workspace:

json
{  "servers": {    "drumbeats": {      "type": "http",      "url": "https://api.drumbeats.io/mcp"    }  }}
Other clients

Any client that supports Streamable HTTP with OAuth can connect. Give it the URL and it runs the sign-in (OAuth 2.1 with PKCE).

On your machine, with an API key

Create a key at drumbeats.io/account/api-keys. An account key covers every project you own or belong to. A project key limits the server to one project.

Claude Desktop

Download drumbeats-mcp-vX.Y.Z.mcpb from the latest release, open it, and paste your key when Claude Desktop asks.

Claude Code
bash
claude mcp add drumbeats -e DRUMBEATS_API_KEY=dk_your_key -- npx -y @drumbeats/mcp
Cursor and other clients
json
{  "mcpServers": {    "drumbeats": {      "command": "npx",      "args": ["-y", "@drumbeats/mcp"],      "env": { "DRUMBEATS_API_KEY": "dk_your_key" }    }  }}
VS Code

Add this to .vscode/mcp.json in your workspace:

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

Running it with npx needs Node.js 22.

Tools

The "Needs" column is the permission the tool requires: the scope of your API key, or what you approve when you sign in to the hosted server.

Monitors and projects (9 tools)
ToolWhat it doesNeeds
list_projectsLists the projects you can access, with their alert channels and groups.read
create_projectCreates a project. Needs an account key.manage_projects
update_projectChanges a project's name or description.manage_projects
create_monitorCreates a cron, heartbeat or HTTP uptime monitor.manage_monitors
list_monitorsLists a project's monitors with their type, status and schedule.read
get_monitorShows one monitor and its full settings.read
update_monitorChanges some settings of a monitor and keeps the rest.manage_monitors
pause_monitorStops a monitor's checks and alerts.manage_monitors
resume_monitorStarts a paused monitor again.manage_monitors
Report job runs (3 tools)
ToolWhat it doesNeeds
ping_startReports that a job started and returns a run_id for its finish.manage_monitors
ping_successReports that a job finished. This is the ping that keeps a monitor up.manage_monitors
ping_failureReports that a job failed, which can open an incident and alert.manage_monitors

Each takes the monitor's id plus an optional run_id, message and payload. They do the same as calling the monitor's ping URL, which helps when an agent can't make outbound HTTP requests, as in Claude Code cloud scheduled tasks.

History and incidents (4 tools)
ToolWhat it doesNeeds
get_monitor_historyShows a monitor's recent pings, checks and response times.read
get_uptime_summaryShows uptime for every monitor in a project.read
list_incidentsLists incidents, filtered by status or monitor.read
manage_incidentShows, acknowledges or resolves an incident.manage_monitors
Checks that need no account (3 tools)
ToolWhat it does
check_httpRequests a URL and reports the status code and response time.
check_sslReads a site's TLS certificate: whether it is valid, when it expires, who issued it.
check_dnsLooks up a hostname's DNS records.

These work with no Drumbeats account or key. Add the server through npx without DRUMBEATS_API_KEY and ask whether your site is up.

Things to ask

text
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 the certificate for example.com expire?

Configuration

These apply when you run the server with npx. The hosted server needs none of them.

VariableDefaultWhat it does
DRUMBEATS_API_KEYnoneYour API key (dk_…). Needed for every tool except the three checks.
DRUMBEATS_API_TIMEOUT_MS15000How long to wait for the Drumbeats API, in milliseconds.
DRUMBEATS_API_BASE_URLhttps://api.drumbeats.ioThe API the server talks to.

Development

Use the Node.js version in .nvmrc.

bash
npm ci          # install dependenciesnpm run build   # compile to dist/npm run lint    # Biome lint and format checknpm test        # run the tests

CONTRIBUTING.md covers pull requests and RELEASING.md covers releases. Please report security problems privately, as described in SECURITY.md.

License

Apache-2.0. Copyright 2026 Lucky S Software, see NOTICE. Drumbeats is made by Lucky S Software.

Source: README.md at commit 2a6b876

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.5.2LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts