# EZO Watcher

> EZO Watcher is an open-source MCP server for developer tools. Self-hosted monitoring that your coding agent sets up, proves and fixes through MCP. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, self-hosted, Web, Linux, macOS
- **Website:** https://ezo-watcher-demo.pages.dev
- **Repository:** https://github.com/ezolabs/ezo-watcher
- **MCP Registry name:** io.github.ezolabs/ezo-watcher
- **Categories:** developer tools, cloud and infrastructure
- **Listing updated:** 2026-11-14

## About

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.

## Features

- **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

## Install

### Claude Code (Terminal)

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

### Claude Desktop (claude_desktop_config.json)

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

### Cursor (~/.cursor/mcp.json)

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

### VS Code (.vscode/mcp.json)

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

### Windsurf (~/.codeium/windsurf/mcp_config.json)

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

### Other clients (your client's MCP settings (most use this shape))

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

## 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

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/ezo-watcher
