About Drumbeats Mcp
The official Drumbeats MCP server lets AI clients manage monitors, inspect run history, and handle incidents. It also offers HTTP, SSL, and DNS checks that require no account.
Key features
- 01Create and manage cron and uptime monitors
- 02Report job starts, successes, and failures
- 03View monitor history and uptime
- 04List, acknowledge, and resolve incidents
- 05Run HTTP, SSL, and DNS checks without an account
Use cases
- 01Track scheduled backups and report their run status
- 02Investigate an unreachable site or expiring certificate
- 03Review uptime and handle open incidents
MCP support
It offers a hosted Streamable HTTP service and a local run mode, exposing Drumbeats project, monitor, job-reporting, and incident tools to MCP clients. HTTP, SSL, and DNS checks need no account.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.drumbeats.io/mcpclaude mcp add --transport http drumbeats-io https://api.drumbeats.io/mcp{"mcpServers":{"drumbeats-io":{"type":"http","url":"https://api.drumbeats.io/mcp"}}}Open in Cursor{"servers":{"drumbeats-io":{"type":"http","url":"https://api.drumbeats.io/mcp"}}}Open in VS Code{"mcpServers":{"drumbeats-io":{"type":"http","url":"https://api.drumbeats.io/mcp"}}}{"mcpServers":{"drumbeats-io":{"serverUrl":"https://api.drumbeats.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
14| Parameter | Type | Required | Description |
|---|---|---|---|
| include | array | No | Optionally also fetch, per project, its notification channels and/or groups. Their ids are needed to wire alerts when creating a monitor. |
Details
From the project README
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)
| Tool | What it does | Needs |
|---|---|---|
list_projects | Lists the projects you can access, with their alert channels and groups. | read |
create_project | Creates a project. Needs an account key. | manage_projects |
update_project | Changes a project's name or description. | manage_projects |
create_monitor | Creates a cron, heartbeat or HTTP uptime monitor. | manage_monitors |
list_monitors | Lists a project's monitors with their type, status and schedule. | read |
get_monitor | Shows one monitor and its full settings. | read |
update_monitor | Changes some settings of a monitor and keeps the rest. | manage_monitors |
pause_monitor | Stops a monitor's checks and alerts. | manage_monitors |
resume_monitor | Starts a paused monitor again. | manage_monitors |
Report job runs (3 tools)
| Tool | What it does | Needs |
|---|---|---|
ping_start | Reports that a job started and returns a run_id for its finish. | manage_monitors |
ping_success | Reports that a job finished. This is the ping that keeps a monitor up. | manage_monitors |
ping_failure | Reports 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)
| Tool | What it does | Needs |
|---|---|---|
get_monitor_history | Shows a monitor's recent pings, checks and response times. | read |
get_uptime_summary | Shows uptime for every monitor in a project. | read |
list_incidents | Lists incidents, filtered by status or monitor. | read |
manage_incident | Shows, acknowledges or resolves an incident. | manage_monitors |
Checks that need no account (3 tools)
| Tool | What it does |
|---|---|
check_http | Requests a URL and reports the status code and response time. |
check_ssl | Reads a site's TLS certificate: whether it is valid, when it expires, who issued it. |
check_dns | Looks 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
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.
| Variable | Default | What it does |
|---|---|---|
DRUMBEATS_API_KEY | none | Your API key (dk_…). Needed for every tool except the three checks. |
DRUMBEATS_API_TIMEOUT_MS | 15000 | How long to wait for the Drumbeats API, in milliseconds. |
DRUMBEATS_API_BASE_URL | https://api.drumbeats.io | The API the server talks to. |
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.