Changeflow MCP server - monitor any website and get AI-enriched change intelligence. Manage sources, search changes, create monitors.
Most developer tooling work still happens through a UI a human drives. Changeflow MCP MCP server moves it into the conversation instead. Changeflow MCP server - monitor any website and get AI-enriched change intelligence. Manage sources, search changes, create monitors.
Monitor any website and get AI-enriched change intelligence via MCP. Manage sources, search changes, and automate web monitoring from Claude, Harvey, or any MCP client.
Changeflow is an enterprise web intelligence platform. It monitors web pages, PDFs, RSS feeds, and APIs for changes, then uses AI to tell you what changed, why it matters, and what to do about it. Used by compliance teams, legal researchers, competitive intelligence analysts, and procurement teams at Fortune 500 companies and Am Law 200 firms.
The server publishes 6 tools. What each one is for:
list_sources — List all your monitored sources with status, tags, and check frequencyget_source — The get_source tool exposed by this serverget_changes — Search and list recent changes across your monitored sourcesget_change — Get full details of a single change including AI summary and structured diffcreate_source — The create_source tool exposed by this servercheck_source — The check_source tool exposed by this serverConfiguration is passed through the environment: CHANGEFLOW_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
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. Changeflow MCP's toolset — list_sources, get_source, get_changes and 3 more — is a fair guide to whether it matches your workflow. It is maintained by stevebutterworth; 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.
| Tool | What it does |
|---|---|
| list_sources | List all your monitored sources with status, tags, and check frequency. |
| get_source | The get_source tool exposed by this server. |
| get_changes | Search and list recent changes across your monitored sources. |
| get_change | Get full details of a single change including AI summary and structured diff. |
| create_source | The create_source tool exposed by this server. |
| check_source | The check_source tool exposed by this server. |
{
"mcpServers": {
"changeflow": {
"command": "npx",
"args": ["changeflow-mcp-server"],
"env": {
"CHANGEFLOW_API_TOKEN": "your_api_token_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHANGEFLOW_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.