Bimhouse MCP Server

by bim Your server? Claim it

answering

Bimhouse is answering right now. Last checked 13 min ago. It exposes 29 tools.

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

Uptime history 52 days of history · worst day 0%

52 days agonow

98.9%

Uptime 24h

90 of 91 checks

Tools

read from the server

603 ms

Response time

average over 24h

open, no key

Access

streamable-http

Bimhouse does not always answer

Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.bimhouse]
url = "https://bim.house/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 29

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

house

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). / 新しい物件 (bim.json) を作成する。name か address のどちらか必須 — 住所だけ渡せば geocode で座標を引き「<地名>の家」と自動命名して家が建つ (REINFOLIB_KEY 設定時は用途地域も実値注入)。elements (bim.json v1 要素配列) を渡すとそのまま保存、省略すると敷地寸法から住宅 BIM を自動生成。name/rooms に「薪ストーブ・土間・ロフト・カーポート・書斎・ピアノ・サウナ」等の言葉が入ると対応する要素 (煙突・炉台・はしご込み) を自動配置し、寒冷地住所ならトリプルガラス+付加断熱+雪止めに外皮を格上げ。「平屋」「2階建て」も階数に反映。slug と edit_token、viewer/json/permit URL と適用 features・site (座標/用途地域ソース) を返す。

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 でメタのみ。

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 要素配列) を渡すと差し替え、project (object) でメタ (name/construction_jpy/proposed_gross_m2 等) のみ更新も可。get_house_bim で現状を取得 → 編集 → update_house → 返り値の houki (法規再判定) を確認、のループで自分の LLM だけで設計改善が完結する。保存ごとに履歴 (bim_versions) が残る。

product

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 に即反映。既存 SKU の上書きは不可 (insert-only)。

get_product

[EN] Get one product's full detail by SKU (price, U-value/η, stock, JAN, successor). / SKU を指定して 1 製品の詳細 (価格・性能値 U値/η値・在庫・JAN・後継品) を取得。

update_product

[EN] Update fields of a product you created (needs Bearer API key; your SKUs only). / 自分が create_product で登録した製品のフィールドを更新する。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は更新不可。指定したフィールドのみ上書き。

houki

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 を渡すとその物件の有効敷地条件 + 法規判定も同梱。

houki_check

[EN] Run the Japanese Building Standards Act check (coverage, FAR, slopes, daylight, ventilation) and return pass/fail. / 建築基準法チェック (建ぺい率・容積率・北側/道路斜線・採光・換気) を houki-engine で実行し合否を返す。

place

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 viewer / GET /api/projects/<slug>/furnishings resolves these at view time so stock is always live and never duplicated. / 家に MU(wearmu.com の作ったもの) や device.house(言葉で動く実機) の在庫を *参照* で置く。edit_token 必須。複製せずポインタだけ持ち、表示時に各サービスをライブ解決する(常に最新・売れたら消える)。source='mu' は brand slug(例 biruwa)、source='device' は部屋キー(entrance/living/bedroom/kitchen/outdoor/any)。

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/検査リストを同梱。

site

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 が使う物件の有効敷地条件を取得 (用途地域・道路幅員・高度/防火地区・気候区分・緯度・隣地距離・敷地面積最低限度・日影規制)。

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_check に反映する。edit_token 認証が必要。指定したフィールドのみ更新し、再判定した houki を返す。既定値による誤 NG (例: 前面道路幅員) を実値で是正できる。

admin

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_regulation?}]. DB + cache applied immediately. For operators to backfill zoning/road-width (e.g. from reinfolib) across all properties. / 任意の物件の敷地条件を一括上書き (管理者のみ・edit_token 不要)。entries 配列で複数物件をまとめて投入。DB+キャッシュ即時反映。用途地域/道路幅員等の実データを全物件へ流し込む運用者向け。

build

get_build_plan

[EN] Construction plan for a house: schedule (Gantt) + per-trade order packages (cost, lead, region-driven spec constraints, inspection checklist). / 物件の施工計画。工種(こうしゅ)別に工程(ガント) + 発注パッケージ(概算・工期・地域由来の仕様制約・検査チェックリスト) を返す。見積を工種に割って自動生成。

catalog

search_catalog

[EN] Search the building-materials catalog (3,900+ SKUs) by keyword/brand/category. / bim.house の建材・設備カタログ (3,900+ SKU) を検索。窓/断熱/設備/家具などを brand・category・キーワードで絞り込む。

chat

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 でチャージ。建築・BIM・法規・SIPs・MU について日本語で答える。引数 message (必須) と history (任意, [{role, content}])。

contractors

list_contractors

[EN] List registered contractors, optionally filtered by prefecture/trade. / 登録業者の一覧。都道府県・工種で絞り込み可。

forkable

set_forkable

[EN] Allow or forbid others from forking (copying) a house (needs edit_token). / 他者がこの物件をフォーク (コピー) できるかを切り替える。edit_token が必要。forkable=false で他者のコピー作成を禁止 (既定は全て可)。

houses

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_user=true で公開ユーザー物件も含める。

incomplete

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. / 住所が不完全 (町名欠落・プレースホルダ) な公開物件を一覧する。管理者のみ。直すと座標から用途地域を判定でき投入できる。

match

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棟の発注が地域の複数業者に自然に分かれる。

material

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) と在庫、クリティカルパス納期も返す。

mine

list_mine

[EN] List products you registered (needs Bearer API key). / 自分 (API キーのアカウント) が登録した製品の一覧を返す。Authorization: Bearer <APIキー> 必須。

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 か lat/lng+service_radius_km。

retire

retire_product

[EN] Retire (discontinue) a product you created (needs Bearer API key; soft, not hard delete). / 自分が登録した製品を取り下げる (生産終了化。ハード削除はしない)。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は不可。

upsert

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) に一致する全物件の houki に反映。

visibility

set_visibility

[EN] Toggle a house's public listing on/off (needs edit_token). / 物件の掲載/非掲載を切り替える。edit_token (create_house の返り値) が必要。private=true で物件一覧から非掲載 (直リンクは残る)。進化ループの低スコア物件の淘汰などに使う。

whoami

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 どちらからでも使える。

zoning

delete_zoning_rule

[EN] Remove a zoning rule override (reverts to engine defaults) — admin only. / 用途地域規制ルールの上書きを削除し、エンジン既定値に戻す。管理者のみ。

Endpoints

URL	Transport	State	Latency	Checked
https://bim.house/mcp	streamable-http	answering	812 ms	13 min ago

Alternatives to Bimhouse

same job, measured the same way

Structura

by structura

Design domain models and generate deterministic multi-stack code, driven by your coding agent.

answering

Ccboot MCP Server

by rcolkitt

Generate and manage Claude Code configs: CLAUDE.md, skills, agents, hooks, and MCP settings.

25 installs/wk local only

Capitolguide

by capitol

Navigate the U.S. Capitol complex: decode room codes, route buildings, check access, amenities.

9 tools answering

Barcode Scanner

by domdomegg

Scan and generate barcodes and QR codes.

35 installs/wk local only

Repo Graph

by james-chahwan

Structural graph map of any codebase so LLMs navigate by structure, not guesswork.

294 installs/wk local only

Topos

by krv-labs

Structural code-quality tools for AI coding agents.

439 installs/wk local only

Pystub

by koyoyeager

Auto-detect stubbable packages for Python exe builds and generate minimal stub code

85 installs/wk local only

Reuse Before Generate

by aradar46

Checks whether your idea already exists before your agent builds it. Searches GitHub, npm, Python.

36 installs/wk local only

Bimhouse — questions

Answers built from our own checks of this server.

What can Bimhouse do?

It exposes 29 tools, read directly from the server on our last check. Among them: admin_set_site_context, chat, create_house, create_product, delete_zoning_rule, get_build_plan and 23 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Bimhouse mostly used for?

Its tools cluster around product, house and place. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Bimhouse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 603 ms. The bar chart above shows every period we have measured.

How do I connect Bimhouse?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Bimhouse need an API key?

No. Bimhouse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 29 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Bimhouse?

It answers our handshake in 603 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.