for vs code and copilot agent mode
Connect VS Code to your uptime monitoring
VS Code adds the server as type http, signs you in through the browser, and comes back on a loopback port. Commit the config to .vscode/mcp.json and the whole team gets the server with the repo, each person signing in as themselves. Confirmations render as native VS Code dialogs, so the 15 tools that act are offered and each one asks.
Add it as an HTTP server
Open the Command Palette, run MCP: Add Server, choose HTTP, and paste https://mcp.uptimepage.dev/mcp. Or write the config below into .vscode/mcp.json. On first use VS Code registers itself with the Uptimepage authorization server, opens your browser on the login and consent screen, and returns on a loopback port. Approve once; the connection lives as long as you chose on that screen, 30 to 365 days, and refreshes itself in between.
In Copilot agent mode
Once the server is running, its tools show in the tools picker of agent mode and the agent calls them like any other. VS Code supports MCP elicitation, so the server lists all 31 tools and every write shows its confirmation as a native dialog: the monitor about to be created, with the result of the check it already ran; the incident about to be resolved; the update about to be posted. Cancel the dialog and nothing happens. There is no remember-my-choice.
Per repo, per person
A .vscode/mcp.json checked into the repo gives every teammate the server the moment they open the workspace, and each of them signs in with their own Uptimepage login, so tokens are personal and revoked one at a time. Put the same file in your user profile instead if you want the server in every workspace. Either way the connection is bound to one organization, the one active in the app when you approved, and the consent screen names it.
Prompts that fit an editor
"Which of our monitors is failing, and from which region?" reads org health and the per-region split. "Show me the full config of the monitor for this service" returns what the check asserts: expected status, body match, timeout, TLS options, regions, and which channels it alerts, with credentials masked. "Run the check on staging now" runs it behind a prompt and returns the result. "Create a status page for the API and add the two public monitors to it" is two confirmations, then a page you enable when ready.
What it never gets
The agent cannot paste a credential onto a monitor. A request header that carries one must reference an org variable, as Bearer {{ api_key }}, so the secret never crosses the chat; the basic-auth and bearer fields and browser flow passwords are set in the app only, and a URL with a password in it is refused. It cannot create a notification channel either, because that means carrying a webhook or a bot token through the chat. It can bind a monitor to a channel you already made, by name. Header values and request bodies come back masked when it reads a monitor, and what a browser flow types is never returned.
.vscode/mcp.json
{
"servers": {
"uptimepage": {
"type": "http",
"url": "https://mcp.uptimepage.dev/mcp"
}
}
}FAQ
How do I add the server in VS Code?
Does it work in Copilot agent mode?
Can I commit the config so the team gets it?
At a glance
- Server URL https://mcp.uptimepage.dev/mcp
- Where MCP: Add Server, or .vscode/mcp.json
- Transport http, streamable
- Sign-in OAuth in the browser, back on 127.0.0.1
- Confirmations native dialogs, all 31 tools offered
- Shared with the team commit .vscode/mcp.json
- Price to start free, no card