Drumbeats Io MCP

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:

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:

{

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

VS Code

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

{

"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

claude mcp add drumbeats -e DRUMBEATS_API_KEY=dk_your_key -- npx -y @drumbeats/mcp

Cursor and other clients

{

"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:

{

"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)

Report job runs (3 tools)

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)

Checks that need no account (3 tools)

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

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.

Development

Use the Node.js version in .nvmrc.

npm ci          # install dependencies

npm run build # compile to dist/ npm run lint # Biome lint and format check npm 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.