listMonitorsLABSCO SUMMARY
Incident history per endpoint is the question worth asking.
Whether something is up right now is a dashboard's job. What a conversation is better at is the follow-up — what happened to this endpoint over the last month, how long each outage lasted, is this the third time. Having incidents queryable by monitor is what makes that answerable in one turn. Creating monitors from a description is the other genuinely convenient bit: adding an endpoint mid-conversation is faster than any form.
What it is
An MCP server that connects an Uptime Agent monitoring account to an assistant. Uptime Agent watches websites and API endpoints and alerts when they fail; this puts the monitors and the incident record behind a conversation, and lets a new endpoint be added by saying so.
What you get
- Every monitoring endpoint listed, and one read in detail by id —
listMonitors,getMonitor - A new endpoint set up with a name, a URL, a tracking type such as http or ping, and a check frequency in seconds —
createMonitor - Detected downtime incidents listed, and one read in detail by id —
listIncidents,getIncident - All incidents for one specific endpoint, which is how you see whether a service has a history —
listIncidentsByMonitor - Public tracking created without authentication for a URL you want watched —
createAnonymousTracking
Requirements
An active Uptime Agent account and an API key: log in to the dashboard, go to Account then API Keys, create one with the permissions you need and copy it. Node.js 18 or higher. The quickest install is npx uptime-agent-mcp setup, which installs the server, configures it for Claude Desktop and prompts for the key; Smithery is an alternative. To do it by hand: clone, npm install, npm run build, and put UPTIME_API_KEY in a .env file, with PORT optional and defaulting to 3000. A Docker configuration is documented for clients that prefer it. Published as uptime-agent-mcp (0.0.10), MIT licensed.
Setup effort
One command plus a key — npx uptime-agent-mcp setup, then supply credentials
USE CASES
01
Finding out what broke and for how long
List recent incidents and read the details, instead of piecing the timeline together from alerts.
02
Checking whether one service keeps failing
Pull every incident for that monitor and see the pattern rather than the latest event.
03
Adding a new endpoint to watch
Describe the URL, the check type and the frequency, and have the monitor created without opening the dashboard.
04
Reviewing what is being monitored at all
List the monitors to see what coverage actually exists before assuming something was being watched.
7 tools
Listed in project docs. Your client may show a different list.
getMonitorcreateMonitorlistIncidentsgetIncidentlistIncidentsByMonitorcreateAnonymousTrackingBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18
- UPTIME_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx uptime-agent-mcp setupMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"uptime-agent": {
"command": "npx",
"args": [
"-y",
"uptime-agent-mcp"
],
"env": {
"UPTIME_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"uptime-agent": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"UPTIME_API_KEY",
"uptime-agent-mcp"
],
"env": {
"UPTIME_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
