About uptimemonitoring
uptimemonitoring provides runnable examples for managing uptime monitors across command-line, Node.js, Python, GitHub Actions, MCP, and webhooks. Its MCP examples let users manage monitors in Claude Code and Cursor using natural language.
Key features
- 01Create, list, test, and delete monitors
- 02Manage monitors in Claude Code
- 03Manage monitors in Cursor
- 04Add post-deploy health checks
- 05Receive monitor status webhooks
Use cases
- 01Manage monitors from an MCP-compatible coding environment
- 02Test a monitor during setup
- 03Gate deployment on service health
- 04Send notifications for outages and recoveries
MCP support
Includes setup examples for managing monitors through MCP in Claude Code and Cursor. The README does not specify the MCP tools or transport.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.uptimemonitoring.com/mcpclaude mcp add --transport http com-uptimemonitoring https://api.uptimemonitoring.com/mcp{"mcpServers":{"com-uptimemonitoring":{"type":"http","url":"https://api.uptimemonitoring.com/mcp"}}}Open in Cursor{"servers":{"com-uptimemonitoring":{"type":"http","url":"https://api.uptimemonitoring.com/mcp"}}}Open in VS Code{"mcpServers":{"com-uptimemonitoring":{"type":"http","url":"https://api.uptimemonitoring.com/mcp"}}}{"mcpServers":{"com-uptimemonitoring":{"serverUrl":"https://api.uptimemonitoring.com/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.
https://api.uptimemonitoring.com/mcpAuth requiredTools
Details
From the project READMEUptimeMonitoring Examples
Copy-paste-runnable examples for every UptimeMonitoring integration.
Integrations
| Integration | Path | Description |
|---|---|---|
| cURL | curl/ | Create, list, test, and delete monitors from the command line |
| Node.js | node/ | Same lifecycle using Node 20+ native fetch, no dependencies |
| Python | python/ | Same lifecycle using requests |
| GitHub Actions | github-actions/ | Post-deploy health gate with uptimemonitoring/assert-healthy |
| MCP — Claude Code | mcp/claude-code/ | Manage monitors with natural language in Claude Code |
| MCP — Cursor | mcp/cursor/ | Manage monitors with natural language in Cursor |
| Webhooks | webhooks/ | Push notifications when a monitor goes down, recovers, or flaps |
Placeholder convention
All examples use placeholders — replace them with your own values before running:
| Placeholder | Replace with |
|---|---|
UPTIMEMONITORING_API_KEY | Your API key — set as an environment variable, never hardcode it |
umk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx | Your actual API key from Settings → API Keys |
123 | Your monitor's numeric ID (visible in the dashboard URL) |
whs_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx | The HMAC signing secret returned when you set a webhook |
Never commit a real key to version control.
Coming in Phase 2
terraform/— provision and manage monitors as infrastructurekubernetes/— liveness/readiness gate via assert-healthy in a pod lifecycle hookpagerduty-integration/— route monitor alerts to PagerDuty incidents
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.