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