AI HomeDesign MCP

• list_capabilities — List every AI HomeDesign tool this MCP can run, grouped by category. Returns each tool's slug, display name, description and whether it needs one or tw
• list_styles — List the allowed design styles, room types and widget options. With no argument, returns the global style/room/area lists. With a tool_slug, returns tha
• describe_tool — Show the input slots, widgets and selectable options for one tool, plus a ready-to-use example payload for `run_process`. Use this before `run_process`
• create_project — Create a project (a container that groups all work for one property). Returns the new project's `id`.
• list_projects — List your projects (paginated). Optional free-text `search` on address.
• get_project — Fetch a single project by id.
• create_order — Upload one or more images and create an order. Provide `image_urls` (public URLs) and/or `image_base64` (raw base64 or data: URLs) — you can use either.
• get_order — Fetch an order, including its input assets and any processes run on it.
• run_process — Start an AI job on an existing order (full control over every tool). `asset_map` maps each of the tool's input-slot keys to an asset id from the order.
• get_process — Fetch a process: its `status` (pending/processing/done/failed) and, when done, the `final_assets` with downloadable result image URLs. If a webhook resu
• wait_for_result — Poll a process until it is `done` or `failed` (or until timeout), then return the final result image URLs. Respects the API's 5s minimum poll interval.
• virtual_staging — Furnish an EMPTY room photo with AI furniture in a chosen design style. Provide the photo as `image_url` OR `image_base64` (raw base64 or a data: URL).
• interior_design — Fully redesign a FURNISHED room (walls, floors, furniture, decor) in a style. Same workflow as virtual_staging: never pick the style yourself — ask the user

No long description beyond the summary.