changedetection-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHANGEDETECTION_API_KEY | Yes | Your ChangeDetection.io API key | |
| CHANGEDETECTION_BASE_URL | Yes | The base URL of your ChangeDetection.io instance (e.g., http://localhost:5000) | |
| CHANGEDETECTION_MCP_ACTION_LIMIT_PER_WATCH | No | Maximum number of mutating actions allowed per watch after a diff (default: 3, 0 to disable) | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_watchesB | List all watched URLs with their current status. |
| get_watchC | Get detailed information about a specific watch. |
| create_watchC | Create a new URL watch to monitor for changes. |
| update_watchC | Update an existing watch's settings. |
| delete_watchB | Permanently delete a watch and all its history. |
| recheck_watchB | Trigger an immediate recheck of a watch URL. |
| get_watch_historyB | List the snapshot history (timestamps) for a watched URL. |
| get_snapshot_diffC | Get the diff between two snapshots of a watched URL. |
| list_tagsA | List all tag groups used to organise watches. |
| create_tagB | Create a new tag/group for organising watches. |
| search_watchesB | Search watches by URL or title. |
| get_system_infoA | Get ChangeDetection.io server stats and health. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.