what_changed_since — databutler facts MCP Tool
what_changed_since
(what changed since) is one of 3 tools on the
databutler facts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call what_changed_since from your client
- Claude Code databutler facts what_changed_since run in your project directory
- Claude Desktop databutler facts what_changed_since ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor databutler facts what_changed_since ~/.cursor/mcp.json
- VS Code databutler facts what_changed_since .vscode/mcp.json
- Zed databutler facts what_changed_since ~/.config/zed/settings.json
- Windsurf databutler facts what_changed_since ~/.codeium/windsurf/mcp_config.json
- Cline databutler facts what_changed_since ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI databutler facts what_changed_since ~/.gemini/settings.json
- Grok databutler facts what_changed_since .mcp.json (in your project root)
- ChatGPT databutler facts what_changed_since Settings → Connectors → Advanced → Developer mode
- Claude.ai databutler facts what_changed_since Settings → Connectors → Add custom connector
- LangChain databutler facts what_changed_since pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http databutler-facts https://databutler.dev/api/mcp/factsOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.