Connect Cursor
Prerequisites
Section titled “Prerequisites”- Cursor (current stable release)
- An
umk_live_API key from app.uptimemonitoring.com — see Authentication
Connect
Section titled “Connect”Create or open your Cursor MCP config file and add the UptimeMonitoring server block:
- Global (all projects):
~/.cursor/mcp.json - Project-local:
./.cursor/mcp.jsonin your project root
{ "mcpServers": { "uptimemonitoring": { "url": "https://api.uptimemonitoring.com/mcp", "headers": { "Authorization": "Bearer umk_live_..." } } }}Replace umk_live_... with your actual API key. Do not commit a project-local config with a live key — add .cursor/mcp.json to .gitignore before saving.
OAuth alternative
Section titled “OAuth alternative”Cursor supports OAuth for remote MCP servers that advertise OAuth metadata. If the server triggers an OAuth prompt, complete the browser flow rather than adding a manual header.
Verify
Section titled “Verify”Fully restart Cursor (quit and relaunch — killing only the window is not enough). Open the MCP panel and confirm uptimemonitoring appears as connected. Then ask:
list my monitors
Common errors
Section titled “Common errors”| Symptom | Cause | Fix |
|---|---|---|
401 Unauthorized | Missing or incorrect key | Confirm the key starts with umk_live_ and is pasted in full without extra whitespace |
| Server not appearing | Config file in wrong location | Cursor reads only ~/.cursor/mcp.json or ./.cursor/mcp.json |
| Tools not appearing after config change | Cursor not fully restarted | Quit Cursor fully (including background helper) and relaunch |
For end-to-end verification with test monitor creation and deletion, see the detailed Cursor guide.