home_buyer_report — Listing Location Toolkit MCP Tool
home_buyer_report
(home buyer report) is one of 14 tools on the
Listing Location Toolkit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call home_buyer_report from your client
- Claude Code Listing Location Toolkit home_buyer_report run in your project directory
- Claude Desktop Listing Location Toolkit home_buyer_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Listing Location Toolkit home_buyer_report ~/.cursor/mcp.json
- VS Code Listing Location Toolkit home_buyer_report .vscode/mcp.json
- Zed Listing Location Toolkit home_buyer_report ~/.config/zed/settings.json
- Windsurf Listing Location Toolkit home_buyer_report ~/.codeium/windsurf/mcp_config.json
- Cline Listing Location Toolkit home_buyer_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Listing Location Toolkit home_buyer_report ~/.gemini/settings.json
- Grok Listing Location Toolkit home_buyer_report .mcp.json (in your project root)
- ChatGPT Listing Location Toolkit home_buyer_report Settings → Connectors → Advanced → Developer mode
- Claude.ai Listing Location Toolkit home_buyer_report Settings → Connectors → Add custom connector
- LangChain Listing Location Toolkit home_buyer_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http listing-location-toolkit https://listing-location-toolkit.nerolabs.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 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.