ChangeDetection.io MCP Server

io.github.rusty4444Published by GitHub account rusty4444v0.1.0Updated Oct 24, 2026

MCP server for ChangeDetection.io website monitoring and change history.

The publisher's own server: changedetection.io (official)

Overview

AI-generated overview

Lets an assistant manage ChangeDetection.io website watches, browse snapshot history, and diff page changes through the ChangeDetection.io API.

What you can do
Wraps the ChangeDetection.io API so an assistant can create, list, update, delete, and recheck watches, and organise them with tags. It also lists change history snapshots for a watch, returns diffs between two points in time, searches watches by URL or title, and reads server stats. A per-watch action fuse limits follow-up mutating calls after a diff.
When to use it
Use it when you run ChangeDetection.io and want an assistant to set up or audit page monitoring, review what changed on a page, or triage failed watches without using the web UI. It suits self-hosted or SaaS instances that already have an API key.
Requirements
A running ChangeDetection.io instance (self-hosted or SaaS) and an API key from its settings. Runs locally as a PyPI package via uvx or pip, configured with the environment variables CHANGEDETECTION_BASE_URL and CHANGEDETECTION_API_KEY. Network access to the instance is required.
Before you install
The API key in CHANGEDETECTION_API_KEY grants access to the instance and should be kept secret. Tools can create, update, and delete watches, and delete_watch removes a watch and all its history, so destructive calls should be confirmed. The per-watch action fuse (default 3, configurable) only limits mutating calls after a diff and can be disabled.

Installation

In SourceWeft

  1. Open ChangeDetection.io MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ChangeDetection.io MCP Server

[Buy Me A Coffee]

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_diff arms a configurable limit on follow-up mutating actions for that watch so one noisy page cannot cascade into unlimited rechecks or edits
  • Tag Management — Organise watches with tags/groups
  • Search — Full-text search through watches by URL or title
  • System Info — Quick health and stats readout

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

bash
pip install changedetection-mcp

Configuration

Add to your MCP client config (Claude Desktop, Cursor, Hermes Agent, etc.):

json
{  "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:

bash
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

ToolDescription
list_watchesList all watches (optional tag filter, limit/offset)
get_watchGet full details of a single watch
create_watchCreate a new watch from a URL
update_watchUpdate an existing watch (pause, rename, change schedule, etc.)
delete_watchDelete a watch and all its history
recheck_watchTrigger an immediate recheck
get_watch_historyList change history snapshots for a watch
get_snapshot_diffGet diff between two snapshots
search_watchesFull-text search by URL or title
list_tagsList all tags/groups
create_tagCreate a tag for organisation
get_system_infoGet 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_watch
  • update_watch
  • delete_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:

bash
# Default: 3. Set 0 to disable the fuse globally.export CHANGEDETECTION_MCP_ACTION_LIMIT_PER_WATCH=3

Per call, override the default with the optional action_limit argument on get_snapshot_diff:

text
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

bash
git clone https://github.com/rusty4444/changedetection-mcp.gitcd changedetection-mcpuv venvsource .venv/bin/activateuv pip install -e ".[dev]"

License

MIT — see LICENSE.

Source: README.md at commit f708f37

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Changedetection integrations