Uptime.com's New MCP

Uptime.com launched a Model Context Protocol (MCP) server that exposes its website, server, and infrastructure monitoring as tools for AI assistants like Claude, enabling automated check creation, alert management, and status page control. The server supports both stdio and streamable HTTP transports, with authentication via static API tokens or OAuth2 PKCE, and includes an official hosted instance at mcp.uptime.com.

A Model Context Protocol https://modelcontextprotocol.io MCP server for Uptime.com https://uptime.com . It exposes Uptime.com website, server, and infrastructure monitoring as MCP tools, so AI assistants such as Claude can create and manage checks, read alerts and outages, manage status pages, and inspect account usage on your behalf. The server speaks two transports: stdio for local MCP clients like Claude Desktop, Claude Code, and Cursor and streamable HTTP for hosted deployments . It authenticates with a static API bearer token or a browser-based OAuth2 PKCE flow. If you use Claude Code https://claude.com/claude-code , the easiest way in is the uptime-skills https://github.com/uptime-com/uptime-skills plugin. It bundles this MCP server with task-focused skills — curated context and workflows for Uptime.com choosing probe locations, tuning outage sensitivity, picking the right check type for a target — plus a sensible default permission set. The tools alone give Claude the ability to call the API; the skills give it the know-how to use them well, so you get sound monitoring decisions instead of raw API calls. /plugin marketplace add uptime-com/uptime-skills /plugin install uptime@uptime-com Then authenticate browser OAuth, tokens stored and refreshed for you : /mcp See uptime-com/uptime-skills https://github.com/uptime-com/uptime-skills for team and project-level setup. Uptime.com runs an official hosted instance, so you do not have to run anything yourself. Point any streamable-HTTP MCP client at: https://mcp.uptime.com/mcp Authenticate with your Uptime.com API token generate one under Settings → API & Integrations . Example MCP client configuration: { "mcpServers": { "uptime": { "type": "http", "url": "https://mcp.uptime.com/mcp", "headers": { "Authorization": "Bearer <your-api-token " } } } } The endpoint also advertises RFC 9728 https://www.rfc-editor.org/rfc/rfc9728 protected-resource metadata, so OAuth2-capable MCP clients can discover the authorization server https://uptime.com and obtain tokens themselves instead of supplying a static token. Prefer to run it yourself? Continue below. The fastest way to try it is with go run Go 1.26+ and a personal Uptime.com API token. Generate a token in the Uptime.com UI under Settings → API & Integrations , then: export UPTIME BEARER TOKEN=<your-api-token go run github.com/uptime-com/uptime-mcp@latest -transport=stdio Add the server to your MCP client config e.g. claude desktop config.json , Cursor mcp.json , or claude mcp add-json : { "mcpServers": { "uptime": { "command": "uptime-mcp", "args": "-transport=stdio" , "env": { "UPTIME BEARER TOKEN": "<your-api-token " } } } } Replace "command": "uptime-mcp" with the absolute path to a downloaded binary, or run the container image: { "mcpServers": { "uptime": { "command": "docker", "args": "run", "-i", "--rm", "-e", "UPTIME BEARER TOKEN", "ghcr.io/uptime-com/uptime-mcp:latest", "-transport=stdio" , "env": { "UPTIME BEARER TOKEN": "<your-api-token " } } } } Instead of a static token, let the server run a browser-based OAuth2 login on the first tool call. This needs an OAuth application registered in your Uptime.com account a client ID . No token is stored in your config: { "mcpServers": { "uptime": { "command": "uptime-mcp", "args": "-transport=stdio", "-uptime-url=https://uptime.com", "-client-id=<your-client-id " } } } On the first tool call the server opens your browser to complete authorization, then refreshes the token in the background. See Authentication authentication . Download the archive for your platform from the Releases https://github.com/uptime-com/uptime-mcp/releases page Linux, macOS, and Windows on amd64 and arm64 , extract it, and put uptime-mcp on your PATH : tar xzf uptime-mcp <version <os <arch .tar.gz sudo mv uptime-mcp /usr/local/bin/ uptime-mcp -version Published to GitHub Container Registry. Tags: :<version immutable, e.g. :0.16.0 , :latest newest stable release , :main rolling main HEAD . docker pull ghcr.io/uptime-com/uptime-mcp:latest docker run -i --rm -e UPTIME BEARER TOKEN ghcr.io/uptime-com/uptime-mcp:latest -transport=stdio Published as an OCI chart. Per-environment URLs are not baked in; set them at install time. helm install uptime-mcp oci://ghcr.io/uptime-com/uptime-mcp/charts/uptime-mcp \ --set config.uptimeUrl=https://uptime.com go install github.com/uptime-com/uptime-mcp@latest The binary is installed as uptime-mcp in $ go env GOPATH /bin . git clone https://github.com/uptime-com/uptime-mcp.git cd uptime-mcp go build -o uptime-mcp . Configuration is via CLI flags, with environment-variable fallbacks for the sensitive values. | Flag | Env fallback | Default | Description | |---|---|---|---| -transport | — | stdio | Transport mode: stdio or http . | -listen | — | :8080 | HTTP listen address HTTP mode only . | -uptime-url | UPTIME URL | required | Uptime.com instance URL, e.g. https://uptime.com . The API base is <uptime-url /api/v1/ . | -resource-url | UPTIME RESOURCE URL | http://localhost:<port | Public URL of this server, for OAuth2 protected-resource metadata. | -client-id | UPTIME OAUTH CLIENT ID | empty | OAuth2 client ID. | -client-secret | UPTIME OAUTH CLIENT SECRET | empty | OAuth2 client secret confidential clients . | -log-level | — | error | Log level: debug , info , warn , error . | -version | — | — | Print version and commit, then exit. | Token environment variable: | Variable | Description | |---|---| UPTIME BEARER TOKEN | Static Uptime.com API token. Forwarded as-is, without verification or refresh. | Set UPTIME BEARER TOKEN to a pre-obtained Uptime.com API token. Works in both stdio and HTTP modes; the token is forwarded to the Uptime.com API as-is, with no OAuth configuration, verification, or refresh. UPTIME BEARER TOKEN=<your-api-token uptime-mcp -transport=stdio In stdio mode, when UPTIME BEARER TOKEN is not set, the server performs a browser-based OAuth2 PKCE flow lazily, on the first tool call rather than at startup. This keeps the MCP handshake initialize , tools/list fast. It needs -uptime-url and -client-id ; scope api/v1 is requested against <uptime-url /o/authorize/ and <uptime-url /o/token/ , and tokens are refreshed in the background. uptime-mcp -transport=stdio \ -uptime-url=https://uptime.com \ -client-id=<your-client-id In HTTP mode the server is a token passthrough. For each request it resolves a token in this order and forwards it to the Uptime.com API: | Priority | Source | |---|---| | 1 | Authorization: Bearer <token | | 2 | ?token=<token query parameter | | 3 | UPTIME BEARER TOKEN env var | When -uptime-url is set, the server also serves RFC 9728 https://www.rfc-editor.org/rfc/rfc9728 protected-resource metadata at /.well-known/oauth-protected-resource , advertising the Uptime.com authorization server and scopes api/v1 , api/v1:read so OAuth2-capable MCP clients can obtain tokens themselves. uptime-mcp -transport=http -listen=:8080 \ -uptime-url=https://uptime.com \ -client-id=<your-client-id Dynamic Client Registration RFC 7591 is planned, so OAuth2 clients will not need a pre-registered client ID. In HTTP mode the server listens on -listen default :8080 and exposes: POST / — the streamable-HTTP MCP endpoint. GET /healthz — liveness/readiness probe, returns 204 No Content . GET /.well-known/oauth-protected-resource — RFC 9728 metadata only when -uptime-url is set . uptime-mcp -transport=http -listen=:8080 -uptime-url=https://uptime.com curl -i http://localhost:8080/healthz - HTTP/1.1 204 No Content The server registers tools across the Uptime.com domains below. Tool names are stable; use tools/list from your MCP client to see full input schemas. Checks — list, inspect, and manage monitoring checks | Tool | Description | |---|---| list checks | List monitoring checks with optional filtering. | get check | Get details for a specific check. | get check stats | Get uptime statistics for a check. | delete check | Delete a check. | create <type check | Create a check of a given type see below . | update <type check | Update a check of a given type see below . | Supported check types create and update : http , dns , ssl , icmp , tcp , udp , smtp , imap , pop , ssh , ntp , whois , rdap , blacklist , malware , heartbeat , webhook , group , pagespeed , rum , rum2 , cloudstatus , api , transaction . Locations list locations , get location — discover probe-server locations and their IP addresses. Contacts list contacts , get contact , create contact , update contact , delete contact — manage contact groups used for alert notifications. Tags list tags , get tag , create tag , update tag , delete tag . Dashboards list dashboards , get dashboard , create dashboard , update dashboard , delete dashboard . Status pages, components & incidents - Pages: list status pages , get status page , create status page , update status page , delete status page . - Components: list status page components , get status page component , create status page component , update status page component , delete status page component . - Incidents: list status page incidents , get status page incident , create status page incident , update status page incident , delete status page incident . Alerts & outages list alerts , get alert , ignore alert , list outages , get outage . Cloud status list cloudstatus providers , search cloudstatus services — discover cloud providers and services for cloudstatus checks. Account get account usage — account usage and plan limits. Requirements: Go 1.26+. make test run unit tests make e2e run e2e tests requires UPTIME BEARER TOKEN make run/http run the HTTP server locally on :8080 go build -o uptime-mcp . The e2e suite talks to a live Uptime.com account and is build-tagged e2e ; it runs only when you provide a valid UPTIME BEARER TOKEN : UPTIME BEARER TOKEN=<your-api-token make e2e Mocks are generated with mockery https://vektra.github.io/mockery/ v3+ .mockery.yaml . Contributions are welcome. Please open an issue to discuss substantial changes before sending a pull request, keep changes focused, and run make test before submitting. By contributing you agree that your contributions are licensed under the project's MIT license. Licensed under the MIT License /uptime-com/uptime-mcp/blob/main/LICENSE . SPDX-License-Identifier: MIT .