
dend/brick-mcp-app
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
🧱 MCP App for making my brick dreams a reality
概要
Brick Builder MCP App A Three.js MCP App for designing 3D brick constructions inside MCP-enabled hosts like Claude Desktop and Visual Studio Code. Build interactively or let the AI build structures for you through natural language. Quick Start · Connecting · Tools · Extensibility Brick Builder running in Claude, building a structure through natural language The server is the for all scene state. Both the AI (LLM) and the interactive UI mutate state exclusively through MCP tools. The server validates every operation — collision detection, bounds checking, support verification — and returns authoritative results. - : The host creates separate MCP sessions for the LLM and the app iframe. Scene state lives at module level so both sessions read/write the same scene. - : The UI polls brick_get_scene every second to pick up LLM-initiated changes. User-initiated changes (via callServerTool) are reflected instantly.
README
以下は原文 README の抜粋です。原文を見る。
Brick Builder running in Claude, building a structure through natural language
Quick Start
git clone https://github.com//brick-mcp-app.git
cd brick-mcp-app
npm install
npm run build
npm run serve
The server starts at http://localhost:3001/mcp.
Prerequisites
- Node.js 20+
- npm 10+
Commands
| Command | Description |
|---|---|
npm install |
Install dependencies |
npm run build |
Build client (Vite) + server (esbuild) |
npm run serve |
Start server in dev mode (tsx, auto-reload) |
npm run dev |
Watch client + serve concurrently |
npm start |
Build then serve (one command) |
Architecture
The server is the single source of truth for all scene state. Both the AI (LLM) and the interactive UI mutate state exclusively through MCP tools. The server validates every operation — collision detection, bounds checking, support verification — and returns authoritative results.
Key Design Decisions
- Shared module-level state: The host creates separate MCP sessions for the LLM and the app iframe. Scene state lives at module level so both sessions read/write the same scene.
- Polling for cross-session sync: The UI polls
brick_get_sceneevery second to pick up LLM-initiated changes. User-initiated changes (viacallServerTool) are reflected instantly. - Single-brick placement: The LLM places one brick per
brick_placecall and receives the placed brick’s footprint in the response, enabling precise positioning of subsequent bricks.
Connecting to Hosts
[!TIP] You can use Cloudflare Tunnels to expose your locally-hosted server to the internet. This lets you connect from claude.ai or any remote MCP host without port forwarding or VPNs:
インストール
This server does not publish a one-line install command.
Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →