Website change monitoring MCP server — track URL changes, compare snapshots, extract content with CSS selectors. Monitor competitor sites, pricing
Webwatch MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Webwatch MCP directly instead of describing what you should do. Website change monitoring MCP server — track URL changes, compare snapshots, extract content with CSS selectors. Monitor competitor sites, pricing pages, job boards. SQLite-backed with diff history.
Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Webwatch MCP is connected, these are the calls the assistant has available:
watch_url — Add a URL to the watch list with optional CSS selector and labellist_watches — List all monitored URLs with status and statisticscheck_now — Fetch a URL now, compare to previous snapshot, return diffget_changes — Browse change history for one or all watched URLscompare_snapshots — Compare any two snapshots side-by-sideextract_content — One-off content extraction with CSS selectorsYou will need one environment variable: WEBWATCH_DATA_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Webwatch MCP's toolset — watch_url, list_watches, check_now and 3 more — is a fair guide to whether it matches your workflow. It is maintained by leviai-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| watch_url | Add a URL to the watch list with optional CSS selector and label |
| list_watches | List all monitored URLs with status and statistics |
| check_now | Fetch a URL now, compare to previous snapshot, return diff |
| get_changes | Browse change history for one or all watched URLs |
| compare_snapshots | Compare any two snapshots side-by-side |
| extract_content | One-off content extraction with CSS selectors |
Or if installed globally:
```json
{
"mcpServers": {
"webwatch": {
"command": "webwatch-mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WEBWATCH_DATA_DIR | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.