list_sourcesLABSCO SUMMARY
Monitoring you can question, not just receive.
The difference from an alert feed is that the history is queryable: search everything you watch for a term, then open one change and read the diff with an explanation of what moved. Creating a source takes plain English for what to look for, so setup is not selector-writing.
What it is
A control surface over a Changeflow account: the sources you monitor, the changes they have produced, and the ability to add a source or force a check now.
What you get
- Your monitored sources with status, tags and check frequency
- Full detail for one source by its share code
- Recent changes across everything you watch, searchable by keyword, date, type, tag or source
- One change in full, with its summary and structured diff
- A new source created from a URL, with what to watch for written in plain English
- An immediate check on a source rather than waiting for its schedule
Requirements
A Changeflow API token from your account settings. Run it locally through npx with the token in the environment, or point a remote client at the hosted HTTP endpoint with the token as a Bearer header.
Setup effort
One command plus a key — npx changeflow-mcp-server, then supply credentials
USE CASES
01
Watching a regulator's page for a rule you care about
Create the source with what to watch for in your own words, then ask what has come back since.
02
Finding out what actually changed
One change opened in full gives the structured diff and the summary, rather than a notification that something moved.
03
Searching everything you monitor for one term
Keyword search across change content, bounded by date, type or tag — the query you cannot run against an inbox of alerts.
04
Checking a page right now instead of waiting
Force a check when something has been announced and the schedule has not caught up.
05
Auditing what is being monitored and how often
The source list with status and frequency, and one source in detail when the coverage looks wrong.
8 tools
Listed in project docs. Your client may show a different list.
get_sourceget_changesget_changecreate_sourcecheck_sourcepause_sourceresume_sourceBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- npx on PATH
- CHANGEFLOW_API_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx changeflow-mcp-serverHosted endpoint
ENDPOINT URL
https://changeflow.com/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"changeflow": {
"command": "npx",
"args": [
"changeflow-mcp-server"
],
"env": {
"CHANGEFLOW_API_TOKEN": "<YOUR_CHANGEFLOW_API_TOKEN>"
}
}
}
}Any MCP client — Remote
Point a client that supports Streamable HTTP at https://changeflow.com/mcp
Send your Changeflow API token as the header Authorization: Bearer <YOUR_CHANGEFLOW_API_TOKEN> (get the token from your Changeflow account settings)
The endpoint allows 100 requests per hour
