factreason_api_breaking_changes — FactGrid (Renamed to FactReason) MCP Tool
factreason_api_breaking_changes
(factreason api breaking changes) is one of 11 tools on the
FactGrid (Renamed to FactReason)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call factreason_api_breaking_changes from your client
- Claude Code FactGrid (Renamed to FactReason) factreason_api_breaking_changes run in your project directory
- Claude Desktop FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/.cursor/mcp.json
- VS Code FactGrid (Renamed to FactReason) factreason_api_breaking_changes .vscode/mcp.json
- Zed FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/.config/zed/settings.json
- Windsurf FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/.codeium/windsurf/mcp_config.json
- Cline FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FactGrid (Renamed to FactReason) factreason_api_breaking_changes ~/.gemini/settings.json
- Grok FactGrid (Renamed to FactReason) factreason_api_breaking_changes .mcp.json (in your project root)
- ChatGPT FactGrid (Renamed to FactReason) factreason_api_breaking_changes Settings → Connectors → Advanced → Developer mode
- Claude.ai FactGrid (Renamed to FactReason) factreason_api_breaking_changes Settings → Connectors → Add custom connector
- LangChain FactGrid (Renamed to FactReason) factreason_api_breaking_changes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http factgrid https://factgrid.co.uk/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.