Drumbeats MCP
MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
README
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
Fourteen 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.
Monitors & projects
| Tool | What it does |
|---|---|
list_projects |
List the projects your key can access (with notification channels and groups). |
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. |
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 |
Override the API base URL (e.g. for testing). |
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.