Skip to content
MCP server

EZO Watcher

Self-hosted monitoring that your coding agent sets up, proves and fixes through MCP

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, self-hosted, Web
Runs
Locally
Version
0.1.0
Listing updated
3 days ago

About EZO Watcher

EZO Watcher is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

The core idea is that a health route returning {"ok": true} stays green while the database is down or last night's cron job never ran. EZO Watcher is an alert wall and pager for a single project, meant to be configured by the coding agent already working on the code. The agent scans the repo for readiness routes, cron entries, scheduled workflows, Sentry, Grafana and Netdata, adds each signal as a source with the file and line it came from, and proves it.

Proving is done with watcher doctor --live --prove, which pushes each reading past its threshold and fails unless the check turns red. When something breaks, the incident gives the agent a fix brief, and a recheck closes it only when the source reads healthy. The source decides when it is well again, not the agent.

It runs as one Node process with SQLite, serves the wall and speaks MCP, with alerts to ntfy, push, SMS or email. The README describes it as open source, with no account needed. A browser demo with sample data lets you acknowledge, silence and recheck incidents.

Install

Run in a terminal

claude mcp add ezo-watcher --env WATCHER_MCP_TOKEN='<WATCHER_MCP_TOKEN>' -- npx -y ezo-watcher

Add to claude_desktop_config.json

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ],
      "env": {
        "WATCHER_MCP_TOKEN": "<WATCHER_MCP_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ],
      "env": {
        "WATCHER_MCP_TOKEN": "<WATCHER_MCP_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "ezo-watcher": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ],
      "env": {
        "WATCHER_MCP_TOKEN": "<WATCHER_MCP_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ],
      "env": {
        "WATCHER_MCP_TOKEN": "<WATCHER_MCP_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ],
      "env": {
        "WATCHER_MCP_TOKEN": "<WATCHER_MCP_TOKEN>"
      }
    }
  }
}

Configuration

  • WATCHER_MCP_TOKENToken for the running Watcher's /mcp endpoint. When unset it is read from the project's .watcher/.env.

What it does

Repo scan
List the readiness routes, cron entries and monitors a project already exposes.
Proven checks
Fail the install unless each check actually goes red when pushed.
Alert wall and pager
See incidents on a wall and get alerts on a phone.
Agent fix loop
Hand the agent a fix brief and close the incident only on a healthy recheck.
Source traceability
Each source records the file and line it was found at.
Single process
Run one Node process with SQLite and no account.

Good for

  • Let a coding agent set up monitoring for a new project
  • Catch a stuck queue that a basic health route misses
  • Add heartbeats for scheduled jobs
  • Page a phone when a dependency goes down

Pricing

Open source

Open source and self-hosted; no account needed

Prices change. Check ezo-watcher-demo.pages.dev before you buy.

EZO Watcher FAQ

What does it need to run?

One Node process with SQLite, installed from npm with `npm i -g ezo-watcher`.

How does the MCP server authenticate?

With `WATCHER_MCP_TOKEN` for the running Watcher's /mcp endpoint, otherwise read from `.watcher/.env`.

How is a check proven?

`watcher doctor --live --prove` mutates each reading and fails unless the check flips.

Is there a demo?

Yes, a browser demo with sample data lets you acknowledge, silence and recheck incidents.

Is EZO Watcher free?

Yes. EZO Watcher is open source, so you can use and self-host it for free.

How do I add EZO Watcher to Claude Code?

Run this command in your terminal: claude mcp add ezo-watcher --env WATCHER_MCP_TOKEN='<WATCHER_MCP_TOKEN>' -- npx -y ezo-watcher

What are the best alternatives to EZO Watcher?

The closest alternatives to EZO Watcher are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to EZO Watcher

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools