Watchtower MCP Server

Most developer tooling work still happens through a UI a human drives. Watchtower MCP server moves it into the conversation instead. Cost tracking + deep security scanning (live RLS cross-tenant probe, leaked-key verification) for AI builders. MCP server for Claude Code.

The short version

No URL to paste. No data uploaded. No deploy required. Runs locally in your Claude Code agent loop.

The tools it exposes

The server publishes 1 tool. What each one is for:

• Dashboard — The Dashboard tool exposed by this server

Getting it running

The server ships on npm as watchtower-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

• Node.js 18+ - Claude Code (or any MCP-compatible client) - For the RLS audit: a Postgres/Supabase connection string with permission to read schema and (ideally) the authenticated/anon roles. No psql install required.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Watchtower's toolset — Dashboard — is a fair guide to whether it matches your workflow. It is maintained by edentan26; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.