Drumbeats MCP - Uptime & Cron Monitoring¶
What It Is¶
Drumbeats MCP (drumbeats-io/mcp) brings cron/heartbeat monitoring, uptime checks, and incident management to AI agents over MCP. DevOps teams can create monitors, triage alerts, and manage status pages directly from their AI assistant - turning "Is the API down?" into an instant query with diagnostic context.
Tools Available¶
| Tool | Description |
|---|---|
| Monitor CRUD | Create, read, update, delete cron and heartbeat monitors |
| Incident triage | View active incidents, acknowledge, resolve |
| Status pages | Manage public/private status page components |
| Uptime query | Check current status of any monitored endpoint |
Quick Start¶
DRUMBEATS_API_KEY={key} npx -y @drumbeats/mcp
Business Use Cases¶
- Incident response: "Show me all active incidents - what's impacted and who's the on-call?"
- Postmortem prep: "What monitors triggered before the 3:14 AM outage? Timeline the alerts"
- Status automation: "Update the status page to reflect the CDN issue - mark as investigating"
- Health checks: "Run a health check on all production endpoints and flag any with response time > 500ms"
Integration with CorpusIQ¶
CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.
This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.
Limitations¶
- Drumbeats-specific: Requires a Drumbeats account and API key
- No metric queries: Focused on uptime/heartbeat - not a full APM (no CPU, memory, latency percentiles)
- Local-only transport: API-key based, not remote SSE