changedetection-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@changedetection-mcp Show me recent changes to my watched pages"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ChangeDetection.io MCP Server
An MCP (Model Context Protocol) server that gives AI agents native access to ChangeDetection.io — the open-source website change detection and monitoring platform.
Features
Watch Management — Create, list, update, delete, and trigger rechecks on watches
Change History — Browse snapshot history and get diffs between any two points in time
Per-watch action fuse —
get_snapshot_diffarms a configurable limit on follow-up mutating actions for that watch so one noisy page cannot cascade into unlimited rechecks or editsTag Management — Organise watches with tags/groups
Search — Full-text search through watches by URL or title
System Info — Quick health and stats readout
Related MCP server: mult-fetch-mcp-server
Why This Exists
No MCP server existed for ChangeDetection.io despite it being one of the most popular self-hosted tools (31k+ GitHub stars). This server fills that gap, letting AI agents:
"Watch this product page and notify me when it changes"
"Show me all my failed watches"
"What changed on this page yesterday?"
"Set up a watch for this job listing"
Quick Start
Prerequisites
A running ChangeDetection.io instance (self-hosted or SaaS)
An API key from Settings → API
Installation
pip install changedetection-mcpConfiguration
Add to your MCP client config (Claude Desktop, Cursor, Hermes Agent, etc.):
{
"mcpServers": {
"changedetection": {
"command": "changedetection-mcp",
"env": {
"CHANGEDETECTION_BASE_URL": "http://localhost:5000",
"CHANGEDETECTION_API_KEY": "your-api-key-here"
}
}
}
}Usage with Hermes Agent
Create ~/.hermes/skills/changedetection/SKILL.md (see skill/ directory) or configure as an MCP server:
hermes mcp add changedetection --command "changedetection-mcp"
hermes config set changedetection.base_url "http://localhost:5000"
hermes config set changedetection.api_key "your-api-key"API Coverage
Tool | Description |
| List all watches (optional tag filter, limit/offset) |
| Get full details of a single watch |
| Create a new watch from a URL |
| Update an existing watch (pause, rename, change schedule, etc.) |
| Delete a watch and all its history |
| Trigger an immediate recheck |
| List change history snapshots for a watch |
| Get diff between two snapshots |
| Full-text search by URL or title |
| List all tags/groups |
| Create a tag for organisation |
| Get server stats (watch count, uptime, version) |
Safety Fuse: Per-Watch Action Limit
When an agent asks for a page diff, that diff can prompt follow-up actions such as immediate rechecks, watch edits, or deletes. To stop one noisy site from triggering a cascade, get_snapshot_diff arms a per-watch fuse before returning.
By default, each diff allows 3 mutating MCP actions for that watch. The fuse applies to:
recheck_watchupdate_watchdelete_watch
After the budget is exhausted, those tools return a clear blocked message instead of calling the ChangeDetection.io API. The fuse is in-process and per watch UUID; watches without an armed fuse are unaffected.
Configuration:
# Default: 3. Set 0 to disable the fuse globally.
export CHANGEDETECTION_MCP_ACTION_LIMIT_PER_WATCH=3Per call, override the default with the optional action_limit argument on get_snapshot_diff:
get_snapshot_diff(uuid="...", from_timestamp="previous", to_timestamp="latest", action_limit=1)Use action_limit=0 to disable the fuse for that watch, or call get_snapshot_diff again with a higher value to re-arm it.
Development
git clone https://github.com/rusty4444/changedetection-mcp.git
cd changedetection-mcp
uv venv
source .venv/bin/activate
uv pip install -e ".[dev]"License
MIT — see LICENSE.
Available Tools
12 toolscreate_tagB
Create a new tag/group for organising watches.
Inputs: title (required). Returns: result
create_watchC
Create a new URL watch to monitor for changes.
Inputs: url (required), tag, title, paused, +1 more. Returns: result
delete_watchB
Permanently delete a watch and all its history.
Inputs: uuid (required). Returns: result
get_snapshot_diffC
Get the diff between two snapshots of a watched URL.
Inputs: uuid (required), to_timestamp (required), from_timestamp (required), action_limit. Returns: result
get_system_infoA
Get ChangeDetection.io server stats and health.
Inputs: no named parameters. Returns: result
get_watchC
Get detailed information about a specific watch.
Inputs: uuid (required). Returns: result
get_watch_historyB
List the snapshot history (timestamps) for a watched URL.
Inputs: uuid (required). Returns: result
list_tagsA
List all tag groups used to organise watches.
Inputs: no named parameters. Returns: result
list_watchesB
List all watched URLs with their current status.
Inputs: tag. Returns: result
recheck_watchB
Trigger an immediate recheck of a watch URL.
Inputs: uuid (required). Returns: result
search_watchesB
Search watches by URL or title.
Inputs: query (required), tag. Returns: result
update_watchC
Update an existing watch's settings.
Inputs: uuid (required), tag, url, title, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool maps to a distinct resource/action (watch CRUD, recheck, history/diff, tags, search, system info). The only near-overlap is list_watches vs search_watches, but descriptions clearly delineate filtering versus listing all.
All names follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, delete_, recheck_, search_). No stylistic deviations.
12 tools is well-scoped for a change-detection server, covering the essential watch lifecycle, snapshots, tags, and health without bloat.
Core watch lifecycle (CRUD + recheck + history/diff) and search are present, but tag management only supports list/create (no update/delete) and there is no direct snapshot content retrieval beyond diff. These are minor gaps.
Maintenance
Related MCP Connectors
AI-native website, RSS, and API monitoring with MCP change events and alerts.
Web search API and MCP server for developers building AI agents.
AI-powered website change monitoring - manage monitors and alerts via MCP.
Turn any public website into an MCP server for agents to search, read and navigate.
Related MCP Servers
- AlicenseCqualityDmaintenanceAn MCP server that integrates with the Agent.ai API to provide web text extraction, web screenshots, and YouTube transcript capabilities through a dynamic function loading system.1004MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.6165 npm15MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for monitoring website changes. Enables tracking URLs, detecting content changes, comparing snapshots, and extracting content with CSS selectors from an AI assistant.4 npmMIT