Bimhouse MCP server

Bimhouse is an MCP server with 29 tools an agent can call, among them admin_set_site_context, chat, create_house. It answers at https://bim.house/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.

Status

Answering

Tools

Official

yes, served from bim.house

Reliability

6 of 6 checks

Response time

360 ms

Transport

streamable HTTP

Last checked

19 October 2026

bim.house — words become buildings. Generate BIM, check code & structure, quote materials.

Description as the publisher wrote it.

The 29 tools Bimhouse offers

Tool	What it does
`admin_set_site_context`	[EN] Bulk-set site conditions for any houses (admin only, admin_token; no edit_token). Pass `entries`: [{slug, zoning?, road_width_m?, high_district?, fire_district?, climate_zone?, latitude?, neighbor_setback_m?, min_lot_area_m2?, shadow_r Inputs: admin_token, entries, slug
`chat`	[EN] AI chat about architecture/BIM/code/MU. Requires Bearer API key; first ¥300 (5 calls) free. / bim.house / MU の AI チャット。メール認証して /console で発行した API キーで認証必須 (Authorization: Bearer <APIキー>)。未チャージでも初回 ¥300 分 (5 回) は無料、使い切ったら /credits でチャージ。 Inputs: history, message
`create_house`	[EN] Build a new house (bim.json) from an address alone (geocoded, auto-named, climate-aware) or full elements; returns slug + edit_token + viewer/permit URLs + inline houki & structure verdicts. No auth (private by default, rate-limited). Inputs: address, construction_jpy, elements, existing_year_built, floors, gross_m2
`create_product`	[EN] Register a new catalog product SKU (needs Bearer API key; insert-only, no overwrite). / 建材カタログ (products) に新しい製品 SKU を登録する。サッシ/窓/断熱材/照明/設備/家具/ドア等。Authorization: Bearer <APIキー> (/console で発行) が必須。登録後は /catalog と search_catalog に即反映。既存 S Inputs: brand, category, description, eta_value, ifc_class, install_jpy
`delete_zoning_rule`	[EN] Remove a zoning rule override (reverts to engine defaults) — admin only. / 用途地域規制ルールの上書きを削除し、エンジン既定値に戻す。管理者のみ。 Inputs: admin_token, profile, zoning
`get_build_plan`	[EN] Construction plan for a house: schedule (Gantt) + per-trade order packages (cost, lead, region-driven spec constraints, inspection checklist). / 物件の施工計画。工種(こうしゅ)別に工程(ガント) + 発注パッケージ(概算・工期・地域由来の仕様制約・検査チェックリスト) を返す。見積を工種に割って自動生成。 Inputs: slug
`get_houki_rules`	[EN] List the building-code checks the engine runs (law refs) + any active zoning-rule overrides; pass slug to also get that house's effective site conditions + houki verdict. / houki エンジンがチェックする法規項目 (根拠条文) と、登録済みの用途地域規制ルール上書き一覧を返す。slug を渡す Inputs: slug
`get_house_bim`	[EN] Fetch a house's full bim.json v1 (project meta + elements) by slug. / slug を指定して物件の完全な bim.json v1 (project メタ + elements 配列) を取得。include_elements=false でメタのみ。 Inputs: include_elements, slug
`get_product`	[EN] Get one product's full detail by SKU (price, U-value/η, stock, JAN, successor). / SKU を指定して 1 製品の詳細 (価格・性能値 U値/η値・在庫・JAN・後継品) を取得。 Inputs: sku
`get_site_context`	[EN] Get a house's effective site conditions used by houki_check (zoning, road width, high/fire district, climate zone, latitude, neighbor setback, min lot area, shadow regulation). / houki_check が使う物件の有効敷地条件を取得 (用途地域・道路幅員・高度/防火地区・気候区分・緯度・隣 Inputs: slug
`houki_check`	[EN] Run the Japanese Building Standards Act check (coverage, FAR, slopes, daylight, ventilation) and return pass/fail. / 建築基準法チェック (建ぺい率・容積率・北側/道路斜線・採光・換気) を houki-engine で実行し合否を返す。 Inputs: slug
`list_contractors`	[EN] List registered contractors, optionally filtered by prefecture/trade. / 登録業者の一覧。都道府県・工種で絞り込み可。 Inputs: prefecture, trade
`list_houses`	[EN] List curated public houses (famous buildings, landmarks); set include_user=true for public user houses. / 運営 curated 公開物件 (有名建築・巨大ランドマーク・SOLUNA 等) の一覧。slug / 規模 / 要素数 / bim.json 充足率(%) を返す。ユーザー作成物件 (u-*) は既定では含まない (直リンクで個別取得は可)。include Inputs: include_user
`list_incomplete_addresses`	[EN] List public houses whose address is incomplete (missing town name / placeholder), so they can be corrected — admin only. Fixing them lets zoning be derived from coordinates. / 住所が不完全 (町名欠落・プレースホルダ) な公開物件を一覧する。管理者のみ。直すと座標から用途地域を判定でき投入でき Inputs: admin_token, limit
`list_mine`	[EN] List products you registered (needs Bearer API key). / 自分 (API キーのアカウント) が登録した製品の一覧を返す。Authorization: Bearer <APIキー> 必須。
`match_contractors`	[EN] Match contractors to a house by trade × location (prefecture or lat/lng+radius). One house's order naturally splits across local builders. / 工種 × 場所 (都道府県 or 緯度経度+対応半径) で業者をマッチ。trade 省略で全工種を一括。1棟の発注が地域の複数業者に自然に分かれる。 Inputs: slug, trade
`material_quote`	[EN] Catalog-priced cost estimate: BOM, total, ¥/m², lead times and critical path from the BIM takeoff. / カタログ連携の概算見積もり。BIM 要素 takeoff × 建材カタログ実価格 (窓/ドア/設備) + 原単位 (躯体/仕上げ) で BOM・総額・㎡単価を算出し、各資材の納期 (lead_time_days) と在庫、クリティカルパス納期も返す。 Inputs: slug
`place_in_house`	[EN] Place a live reference to another service's catalog into a house (needs edit_token) — not a copy. source 'mu' refs a wearmu.com brand slug (goods made by MU); source 'device' refs a device.house room key (word-driven hardware). The v Inputs: edit_token, ref, room, slug, source
`place_order`	[EN] Create a DRAFT purchase order for one trade of a house to a contractor (does NOT send anything — human sends later). / 物件の1工種を業者へ発注 (ドラフト作成のみ・⚠送信はしない)。spec/検査リストを同梱。 Inputs: contractor_id, slug, trade
`register_contractor`	[EN] Register a contractor (supply side, self-serve). Requires Bearer API key. trades = trade codes or 'all'; location via prefectures and/or lat/lng+service_radius_km. / 業者を登録 (供給側セルフサーブ・API キー必須)。trades=工種 code 配列か 'all'、場所は prefectures か Inputs: contact, fulfillment, lat, lead_time_days, lng, name
`retire_product`	[EN] Retire (discontinue) a product you created (needs Bearer API key; soft, not hard delete). / 自分が登録した製品を取り下げる (生産終了化。ハード削除はしない)。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は不可。 Inputs: sku
`search_catalog`	[EN] Search the building-materials catalog (3,900+ SKUs) by keyword/brand/category. / bim.house の建材・設備カタログ (3,900+ SKU) を検索。窓/断熱/設備/家具などを brand・category・キーワードで絞り込む。 Inputs: brand, category, limit, q
`set_forkable`	[EN] Allow or forbid others from forking (copying) a house (needs edit_token). / 他者がこの物件をフォーク (コピー) できるかを切り替える。edit_token が必要。forkable=false で他者のコピー作成を禁止 (既定は全て可)。 Inputs: edit_token, forkable, slug
`set_site_context`	[EN] Override a house's site conditions for houki_check (needs edit_token). Only provided fields are updated; returns the re-run houki verdict. Fixes false NGs from assumed defaults (e.g. set the real road width). / 物件の敷地条件を上書きして houki_chec Inputs: climate_zone, edit_token, fire_district, high_district, latitude, min_lot_area_m2
`set_visibility`	[EN] Toggle a house's public listing on/off (needs edit_token). / 物件の掲載/非掲載を切り替える。edit_token (create_house の返り値) が必要。private=true で物件一覧から非掲載 (直リンクは残る)。進化ループの低スコア物件の淘汰などに使う。 Inputs: edit_token, private, slug
`update_house`	[EN] Update an existing house's bim.json (needs edit_token): swap elements or patch project meta; returns a re-run houki verdict. Versioned each save. / 既存物件の bim.json を更新する。edit_token (create_house の返り値) が必要。elements (bim.json v1 要素配列) を渡す Inputs: edit_token, elements, elements_json, note, project, slug
`update_product`	[EN] Update fields of a product you created (needs Bearer API key; your SKUs only). / 自分が create_product で登録した製品のフィールドを更新する。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は更新不可。指定したフィールドのみ上書き。 Inputs: brand, category, description, eta_value, install_jpy, jan_code
`upsert_zoning_rule`	[EN] Add/update a zoning regulation rule (coverage/FAR/slope/height limits) — admin only (admin_token). Applies to all houses matching (profile, zoning). / 用途地域の規制ルール (建ぺい/容積/斜線/高さ等) を追加・更新する。管理者のみ (admin_token)。(profile, zoning) に一致する全物件の Inputs: absolute_height_limit_mm, admin_token, coverage_pct, far_pct, far_road_coefficient, north_slope_start_mm
`whoami`	[EN] Verify API-key auth: returns your account email if a valid Bearer key is sent. / API キー認証の確認。Authorization: Bearer <APIキー> (/console で発行) を付けると認証済みアカウントの email を返す。Web/CLI どちらからでも使える。

Add Bimhouse to your AI client

Every block below points at https://bim.house/mcp. Pick your client and copy.

Claude Code: one command in your terminal

claude mcp add --transport http bimhouse https://bim.house/mcp

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "bimhouse": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://bim.house/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "bimhouse": {
      "url": "https://bim.house/mcp"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "bimhouse": {
      "type": "http",
      "url": "https://bim.house/mcp"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "bimhouse": {
      "url": "https://bim.house/mcp"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "bimhouse": {
      "serverUrl": "https://bim.house/mcp"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "bimhouse": {
      "url": "https://bim.house/mcp"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: Bimhouse
version: 0.0.1
schema: v1
mcpServers:
  - name: Bimhouse
    type: streamable-http
    url: https://bim.house/mcp

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "bimhouse": {
      "httpUrl": "https://bim.house/mcp"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "bimhouse": {
      "type": "http",
      "url": "https://bim.house/mcp"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "bimhouse": {
      "url": "https://bim.house/mcp"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fbim.house%2Fmcp&type=streamable_http&id=bimhouse&name=Bimhouse

Is Bimhouse up right now?

It answered our last check on 19 October 2026 in 360 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Bimhouse

Sitelas0 tools Websitepublisher0 tools Plyo0 tools Earth LinC0 tools Market Data3 tools Zine0 tools

Questions about Bimhouse

Is there an official Bimhouse MCP server?

Yes. It is published by bim.house and served from bim.house, the vendor's own domain: https://bim.house/mcp.

How many tools does Bimhouse have?

29, as returned by the server's own tools/list on 12 September 2026: admin_set_site_context, chat, create_house, create_product, delete_zoning_rule, get_build_plan, get_houki_rules, get_house_bim, and 21 more.

Is Bimhouse down?

It answered our last check on 19 October 2026 in 360 ms. Over 6 checks since 10 September 2026 it answered 6.

How do I add Bimhouse to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://bim.house/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Bimhouse need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: house.bim. Endpoint host: bim.house. ARD identifier: urn:air:house.bim:mcp:bimhouse. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.