Drumbeats Mcp
@drumbeats-io
Operate Drumbeats monitoring from any AI client — create cron/heartbeat and uptime monitors, triage incidents, and run HTTP/SSL/DNS diagnostics (no account needed for diagnostics).
Overview
What is Drumbeats Mcp?
The official MCP server for Drumbeats — cron, uptime, and heartbeat monitoring plus status pages, operated from Claude, Cursor, VS Code, or any MCP client.
How to use Drumbeats Mcp?
Configure as a remote server (OAuth, no API key) via streamable HTTP: claude mcp add --transport http drumbeats https://api.drumbeats.io/mcp. Or run locally with npx: npx -y @drumbeats/mcp and set DRUMBEATS_API_KEY in the environment. Omit the API key to use only the diagnostics tools.
Key features of Drumbeats Mcp
- Create and manage cron, heartbeat, and HTTP monitors
- Check history, uptime SLAs, and incidents
- Ad‑hoc HTTP, SSL, and DNS checks (no account needed)
- Operate from any MCP client
- Supports both hosted (OAuth) and local (API key) setups
Use cases of Drumbeats Mcp
- Set up and manage monitors using plain language commands
- Review monitor history, uptime summaries, and incidents
- Perform quick diagnostic checks directly from chat
- Integrate monitoring into MCP‑aware IDEs like VS Code or Cursor
FAQ from Drumbeats Mcp
What can Drumbeats Mcp do?
It provides tools for monitor creation (create_monitor, list_monitors, etc.), observation (get_monitor_history, get_uptime_summary, list_incidents), and ad‑hoc diagnostics (check_http, check_ssl, check_dns).
Do I need an API key to use Drumbeats Mcp?
No. The hosted version uses OAuth with no API key. For local use you can provide a DRUMBEATS_API_KEY, or omit it entirely to use only the free diagnostics tools.
What transports are supported?
Streamable HTTP (for hosted OAuth) and standard stdio (for local npm installation).
Where can I get an API key?
Get a free API key from your Drumbeats account at https://drumbeats.io.
Is the server open source?
Yes, the source is available on GitHub under the Apache‑2.0 license.
