io.github.drumbeats-io/mcp
Manage Drumbeats cron, heartbeat and uptime monitors, report job runs and handle incidents.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http io-github-drumbeats-io-mcp 'https://api.drumbeats.io/mcp'
{
"mcpServers": {
"io-github-drumbeats-io-mcp": {
"type": "http",
"url": "https://api.drumbeats.io/mcp"
}
}
}
@drumbeats/mcpclaude mcp add io-github-drumbeats-io-mcp -e 'DRUMBEATS_API_KEY=<your drumbeats_api_key>' -- npx -y @drumbeats/mcp@0.5.2
{
"mcpServers": {
"io-github-drumbeats-io-mcp": {
"command": "npx",
"args": [
"-y",
"@drumbeats/mcp@0.5.2"
],
"env": {
"DRUMBEATS_API_KEY": "<your drumbeats_api_key>"
}
}
}
}
Variables d'environnement
DRUMBEATS_API_KEYsecret Drumbeats API key (dk_...). Optional: the HTTP, SSL and DNS checks work without one.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Drumbeats MCP
The official Model Context Protocol server for Drumbeats — run your monitoring from any AI client. Create monitors, triage incidents, and run HTTP / SSL / DNS checks in plain language from Claude, Cursor, VS Code, or any MCP-capable tool.
What is Drumbeats?
Drumbeats is heartbeat and uptime monitoring for background jobs and services — cron jobs, queues, scheduled tasks, and HTTP endpoints. If a job stops checking in or a site goes down, Drumbeats alerts you. Create a free account at drumbeats.io.
Install
Add the server to your AI client and set one environment variable — your Drumbeats account API key:
{
"mcpServers": {
"drumbeats": {
"command": "npx",
"args": ["-y", "@drumbeats/mcp"],
"env": { "DRUMBEATS_API_KEY": "dk_your_key" }
}
}
}
- Get a key — at drumbeats.io → Account → API keys. An
account-scoped key (
dk_…) works across every project you own or belong to. - Add the config — paste the block above into your client's MCP config and restart it.
- Ask — "List my monitors."
Claude Desktop: prefer a one-click install — download the latest .mcpb bundle
from the Releases page,
double-click it, and paste your key when prompted.
Requires Node.js 22 when running via npx.
Tools
Nineteen tools over one shared layer. The HTTP / SSL / DNS diagnostics work with no account and no API key — point any client at the server and start checking.
Projects & monitors
| Tool | What it does |
|---|---|
list_projects | List the projects your key can access (with notification channels and groups). |
create_project | Create a new project (account-scoped key with manage_projects). |
update_project | Update a project's name or description (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 (partial patch). |
pause_monitor | Pause a monitor (stops checks and alerts). |
resume_monitor | Resume a paused monitor. |
Heartbeat pings
| Tool | What it does |
|---|---|
ping_start | Report that a job started; returns a run_id to pair with its finish. |
ping_success | Report that a job succeeded (the heartbeat that keeps a monitor up). |
ping_failure | Report that a job failed (can open an incident and alert). |
The ping tools replace a curl to the monitor's ping URL, which helps where outbound
HTTP needs an allowlist (for example Claude Code cloud scheduled tasks). Each takes
monitor_id (the monitor UUID) plus optional run_id, message, and payload. On the
hosted server they need a token with the manage_monitors scope.
Observe & triage
| Tool | What it does |
|---|---|
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), filterable by status or monitor. |
manage_incident | Get, acknowledge, or resolve an incident. |
Diagnostics — no account required
| Tool | What it does |
|---|---|
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. |
Example prompts
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? # no account needed
Is the SSL certificate for example.com about to expire? # no account needed
Try it with zero setup
The check_http, check_ssl, and check_dns tools need no Drumbeats account or API
key. Add the server, leave DRUMBEATS_API_KEY unset, and ask "Is my site up?" before
you sign up. When you're ready for continuous monitoring and alerts,
create a free account.
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
DRUMBEATS_API_KEY | For the monitoring tools | — | Account-scoped key (dk_…). Not needed for the diagnostics tools. |
DRUMBEATS_API_BASE_URL | No | https://api.drumbeats.io | The apex REST URL. The Drumbeats API is split across services by path prefix (/id, /beats, /alerts); the client appends the per-service prefix to this apex per request. |
DRUMBEATS_ID_BASE_URL | No | ${apex}/id | Self-host override: full base URL for the id service. |
DRUMBEATS_BEATS_BASE_URL | No | ${apex}/beats | Self-host override: full base URL for the beats service. |
DRUMBEATS_ALERTS_BASE_URL | No | ${apex}/alerts | Self-host override: full base URL for the alerts service. |
Development
Requires the Node version in .nvmrc.
npm ci # install dependencies
npm run build # compile TypeScript to dist/
npm run lint # Biome lint + format check
npm test # run the test suite
See CONTRIBUTING.md for the contribution workflow and SECURITY.md for the security policy. This is a security product — please report vulnerabilities privately.
Links
- Product: drumbeats.io · sign up
- Issues: github.com/drumbeats-io/mcp/issues
License
Apache-2.0 © Lucky S Software. See NOTICE.
A product by Lucky S Software.
Questions fréquentes
Qu'est-ce que io.github.drumbeats-io/mcp ?
Manage Drumbeats cron, heartbeat and uptime monitors, report job runs and handle incidents.
Comment installer io.github.drumbeats-io/mcp ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http io-github-drumbeats-io-mcp 'https://api.drumbeats.io/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.drumbeats-io/mcp ?
Oui. Il attend DRUMBEATS_API_KEY, à renseigner dans sa configuration.
io.github.drumbeats-io/mcp est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient io.github.drumbeats-io/mcp ?
Il est publié par drumbeats-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.