Product

Automation and API

Manage WatchCat from your code or your AI agent. An MCP server and a REST API cover every resource you manage in the app — behind scoped, owner-controlled API keys.

Start free See pricing
EU flag Hosted in the EU
GDPR-friendly by design
Core monitoring data stays in the EU
01

Create an API key in the app, with a read or read and write scope

02

Connect any MCP-capable assistant, or call the REST API directly

03

Manage the same resources you manage in the UI

04

Every key is scoped to your organization and respects your plan

terminal
# Connect an AI assistant over MCP
$ claude mcp add --transport http watchcat \
https://watchcat.io/mcp \
--header "Authorization: Bearer wc_…"
# …or create a monitor from your pipeline
$ curl -X POST https://watchcat.io/api/v1/service_monitors \
-H "Authorization: Bearer wc_…" \
-d '{"url":"https://example.com"}'
Technical flow

How it works in detail

Set up the MCP server Read the REST API reference

MCP server

  • Connect Claude or any MCP-capable client to a single endpoint and let it work with your monitoring.
  • Tools cover uptime monitors, cron monitors, groups, notification channels, integrations, status pages, status updates, incidents, and usage.
  • A read-only key is offered only the read tools, so an assistant can answer questions without changing anything.

REST API

  • A JSON API under /api/v1 for scripts, CI pipelines, and infrastructure-as-code.
  • Standard create, read, update, and delete, plus pause and resume, cron token regeneration, and resolving incidents.

API keys and scopes

  • Keys are created by an organization owner and shown once, then stored only as a hash.
  • Each key is read-only or read and write — pick the least access a task needs. A read-only key can never change anything, over MCP or REST.
  • Revoke a key at any time and the clients using it stop immediately.

Safe by default

  • Every request is scoped to the key's organization.
  • Plan limits are enforced exactly as they are in the app.
  • Secrets such as webhook URLs and bot tokens are never returned in responses.
Why it matters

Monitoring as part of your pipeline

  • Define monitors as part of your deploy pipeline instead of clicking through the UI
  • Let an AI assistant triage incidents, resolve them, and post status page updates
  • One set of keys, two ways in — MCP for agents, REST for scripts and CI
  • Read-only keys make it safe to give an assistant visibility without write access
Coverage

What you can manage

The same resources you manage in the app, available to agents and scripts.

Set up the MCP server Read the REST API reference
  • Uptime monitors
  • Cron monitors
  • Monitor groups
  • Notification channels
  • Integrations
  • Status pages and updates
  • Incidents
  • Plan usage
Use cases

Typical use cases

  • A deploy pipeline that creates a monitor for every preview environment and removes it on teardown
  • An AI assistant that lists open incidents, resolves the false ones, and posts a status page update
  • A read-only key in a chat bot, so anyone can ask what is down without being able to change anything

Start monitoring for free

5 monitors free · no credit card required

Start free Security details