Bring Uptime Monitoring
to Cursor
Learn how to connect Uptime.com to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Uptime.com MCP Server?
Connect your Uptime.com monitoring account to any AI agent and simplify how you monitor site reliability, manage alerts, and perform root cause analysis through natural conversation.
What you can do
- Check Management — List, create, and update monitor checks (HTTP, API, ICMP) to ensure your services are always online.
- Alert Oversight — Retrieve a history of recent UP/DOWN transitions and stay notified of critical outages.
- Incident Analysis — Get detailed Root Cause Analysis (RCA) for alerts to understand why a failure occurred.
- Performance Metrics — Query uptime statistics and performance data for any specific monitor check.
- Team Coordination — List contact groups and third-party integrations (Slack, PagerDuty) to manage notification flows.
- Infrastructure Monitoring — List global monitoring nodes to understand your testing coverage.
How it works
1. Subscribe to this server
2. Enter your Uptime.com API Token (found in your account settings)
3. Start monitoring your uptime from Claude, Cursor, or any MCP client
Who is this for?
- SRE & DevOps Engineers — quickly retrieve RCA reports and check performance stats via simple AI queries.
- Web Administrators — create new monitor checks and verify site health directly from the workspace.
- Product Owners — monitor uptime metrics and recent alert history to measure service reliability via the AI assistant.
Built-in capabilities (12)
g., HTTP, API). Create a new check
Delete a monitor check
com account. Get account profile
Get check details
Get check statistics
Get alert RCA
List all monitor checks
List contact groups
). List active integrations
List global nodes
List recent monitor alerts
Update a check
Why Cursor?
Cursor's Agent mode turns Uptime.com into an in-editor superpower. Ask Cursor to generate code using live data from Uptime.com and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Uptime.com in Cursor
Uptime.com and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Uptime.com to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Uptime.com in Cursor
The Uptime.com MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Uptime.com for Cursor
Every tool call from Cursor to the Uptime.com MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the reason why my website went down via AI?
Yes! Use the get_root_cause_analysis tool and provide the Alert ID (PK). Your agent will retrieve the detailed RCA report explaining the failure.
How do I create a new HTTP check to monitor a URL?
Use the create_check action. Provide the name, address (URL), and set the check_type to 'HTTP'. The agent will instantly register the new monitor.
Is it possible to see the performance statistics for a monitor?
Absolutely. Run the get_check_stats query with your Check ID to retrieve performance and uptime metrics for that specific service.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.