place_order — bimhouse MCP Tool
place_order
(place order) is one of 29 tools on the
bimhouse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call place_order from your client
- Claude Code bimhouse place_order run in your project directory
- Claude Desktop bimhouse place_order ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bimhouse place_order ~/.cursor/mcp.json
- VS Code bimhouse place_order .vscode/mcp.json
- Zed bimhouse place_order ~/.config/zed/settings.json
- Windsurf bimhouse place_order ~/.codeium/windsurf/mcp_config.json
- Cline bimhouse place_order ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bimhouse place_order ~/.gemini/settings.json
- Grok bimhouse place_order .mcp.json (in your project root)
- ChatGPT bimhouse place_order Settings → Connectors → Advanced → Developer mode
- Claude.ai bimhouse place_order Settings → Connectors → Add custom connector
- LangChain bimhouse place_order pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bimhouse https://bim.house/mcpOther tools on this server
- whoami
- chat
- search_catalog
- get_product
- list_houses
- get_house_bim
- houki_check
- material_quote
- create_house
- create_product
- update_product
- list_mine
- retire_product
- update_house
- set_visibility
- place_in_house
- set_forkable
- get_houki_rules
- get_site_context
- set_site_context
- admin_set_site_context
- list_incomplete_addresses
- upsert_zoning_rule
- delete_zoning_rule
- get_build_plan
- match_contractors
- list_contractors
- register_contractor
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.