bridging_cost_analyser — property finance mcp MCP Tool
bridging_cost_analyser
(bridging cost analyser) is one of 4 tools on the
property finance mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call bridging_cost_analyser from your client
- Claude Code property finance mcp bridging_cost_analyser run in your project directory
- Claude Desktop property finance mcp bridging_cost_analyser ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor property finance mcp bridging_cost_analyser ~/.cursor/mcp.json
- VS Code property finance mcp bridging_cost_analyser .vscode/mcp.json
- Zed property finance mcp bridging_cost_analyser ~/.config/zed/settings.json
- Windsurf property finance mcp bridging_cost_analyser ~/.codeium/windsurf/mcp_config.json
- Cline property finance mcp bridging_cost_analyser ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI property finance mcp bridging_cost_analyser ~/.gemini/settings.json
- Grok property finance mcp bridging_cost_analyser .mcp.json (in your project root)
- ChatGPT property finance mcp bridging_cost_analyser Settings → Connectors → Advanced → Developer mode
- Claude.ai property finance mcp bridging_cost_analyser Settings → Connectors → Add custom connector
- LangChain property finance mcp bridging_cost_analyser pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http property-finance-mcp https://fdc-property-finance-mcp.fdcommercial-uk.workers.dev/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.