for cursor
Connect Cursor to your uptime monitoring
Cursor takes the server by URL, registers itself over OAuth, and opens your browser for a sign-in you already have. After that the agent can ask your monitoring questions from inside the editor: what is down, why that flow failed last night, whether the endpoint you just changed is still up. Writes show a confirmation in Cursor before they run.
Add it by URL
Add a new server from the MCP section of Cursor Settings and give it https://mcp.uptimepage.dev/mcp, or write the config below into mcp.json: ~/.cursor/mcp.json for every project, or .cursor/mcp.json at the root of one repo so the server is there for everyone who opens it, each signing in as themselves. The connection is bound to the organization active in the app when you approve; the consent screen names it. Cursor handles the rest: it discovers the server, registers itself with the Uptimepage authorization server, and opens your browser on the login and consent screen. Approve, and the tools show up in the agent's tool list. Nothing to paste and nothing to rotate.
Why the cursor:// callback is fine
Cursor returns from the sign-in on its own cursor:// scheme, alongside a web callback and a loopback port. Uptimepage admits that scheme by name at registration, and PKCE is mandatory, so a program on your machine that hijacked the cursor:// handler would receive an authorization code it cannot redeem: the code is bound to the verifier Cursor holds. The consent screen says where you go after Approve, and for a native scheme it says so plainly: the app on this computer.
What the agent can do
Cursor has supported MCP elicitation since 1.5, so the server offers all 31 tools: 16 that read and 15 that act, each write behind a prompt Cursor shows you before it runs. Ask about the endpoint you are editing and the agent calls get_monitor for its full config, get_monitor_history for its last 24 hours with timings split into DNS, connect, TLS and first byte, and names the region where it fails if it only fails from one. A monitor it creates runs its check first and shows the result in the confirmation.
Prompts that fit an editor
"Is anything monitored in this repo down right now?" reads org health and filters by the tag you use for the project. "Add a monitor for the health endpoint I just wrote, from the same regions as the others" creates it behind one confirmation, with the trial check result in the prompt. "Why did the login flow fail at 03:10?" reads that run step by step. "Pause the staging monitors while I redeploy, then resume them" pauses behind a prompt and resumes behind another.
.cursor/mcp.json
{
"mcpServers": {
"uptimepage": {
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}
FAQ
Do I need to paste a token into Cursor?
Does Cursor show the confirmation before a write?
Can I share the server with my team through the repo?
Is returning on a cursor:// link safe?
At a glance
- Server URL https://mcp.uptimepage.dev/mcp
- Where Cursor Settings, or mcp.json
- Sign-in OAuth in the browser, back on cursor://
- Token to paste none
- Confirmations Cursor 1.5 and later show them
- Per project .cursor/mcp.json in the repo
- Price to start free, no card