Ask your AI assistant what went down overnight.

The question the dashboard can't answer

MCP - the Model Context Protocol - is an open standard for letting an AI assistant use a tool. An MCP server publishes a list of things it can do, and the assistant calls them when your request needs one. It works in Claude, Cursor, VS Code and the rest, and keeps working when you switch.

UpWatchr's dashboard shows you what is up right now and a 24-hour grid. "What went down while I was asleep, and for how long?" is a different question - the answer is in the stream of status changes UpWatchr records, and the dashboard has no view of it. An assistant can read that stream and answer in a sentence.

What you can ask

• "Which of my sites are down right now?"
• "What changed since this morning?"
• "How much downtime did the shop have in the last 24 hours?"
• "Is the billing API up? Check it now."
• "Start watching https://status.example.com every 30 seconds."
• "Pause the staging checks - we're redeploying."
• "If the shop goes down, would I hear about it on Telegram?"

What the assistant can do

Safe by default

• Off until you turn it on. A fresh install does not listen for assistants. While the switch is off, every request is refused with a message that names the setting, so the assistant can tell you why.
• Read-only until you allow more. Let it change my sites is a second switch, also off. Even "check now" sits behind it: it stores nothing, but it sends a real request to somebody's server from your IP, and a read-only setup did not agree to that.
• Removing always asks. Removing a site throws away its history and there is no undo, so the assistant can only raise the confirmation. You answer it.
• Credentials never leave. Header values - usually the API key a monitored endpoint needs - basic-auth passwords, the SMTP password, the Telegram bot token, the full webhook URL and the full email recipient are never returned. The assistant sees header names and whether a site uses auth, nothing more.
• Never off your PC. The connection listens on 127.0.0.1 only and every request carries a token generated on your machine. Reset it in Settings to cut off anything you connected earlier. Every switch applies at once, with no restart.

Connect an assistant

1. Install UpWatchr 2026.9.3 or later - it updates itself if you already have it.
2. Open Settings > AI assistants and tick Let AI assistants connect to UpWatchr. Tick Let it change my sites too if you want it to add, pause or check sites.
3. Press Connect an assistant, pick yours and press Connect. Restart the assistant, then ask it: which of my sites are down?

Connect an assistant picks the shortest safe route for each one. For Claude Desktop, Cursor, VS Code, Windsurf and Gemini CLI, UpWatchr adds itself to the assistant's settings file - everything already there is kept, a copy is saved first, and removing it again is one button. Claude Code gets a one-line command, and Codex CLI, Antigravity and anything else get the exact steps. Assistants it finds on your PC are listed first.

UpWatchr does not have to be open: the assistant's first request starts it, as a normal window. Turning the switch on places a small upwatchr-mcp.exe in UpWatchr's install folder, and that is what the assistant launches - it always finds the version you have installed, so an update never breaks your setup. ChatGPT and Claude in the browser cannot connect: they reach MCP servers from their own servers, and UpWatchr's runs on your machine.

What it deliberately does not do

• Configure your alert channels or the status page password - those are credentials, and they stay in Settings.
• Reset your statistics - destructive, with no undo.
• Remove a site without asking you, ever.

Common questions

Related

• Server monitor for Windows - what UpWatchr watches, and what it does not
• FAQ - price, data, installing and updating
• UpWatchr compared with UptimeRobot, Uptime Kuma, Pingdom and StatusCake