wadi-mcp

An MCP server that exposes the Wadi house pipeline as agent-native tools, so a coding agent can author, check, and preview a Wadi DSL (.wdl) design without the repo checked out and without the desktop app running. The DSL compiler, the schema + wall/roof geometry, the structural-conventions linter, the 2D renderers, and the example

• reference docs are all bundled in — the only external runtime dependency is the native SVG rasteriser (@resvg/resvg-js).

This is the repo-free way to run the Wadi architect skill. (The wadi-skill scripts — check.sh / preview.sh — do the same thing but need the repo; this server replaces them for agents that speak MCP.)

Tools

| Tool | What it does | | --- | --- | | wadi_check | Compile + validate a .wdl: parse, resolve formulas/grids, schema + wall/roof geometry, and the full structural-conventions registry (C1-C10, plus per-primitive rules like the spiral SP1). Returns pass/fail + errors/warnings. Run after every edit. | | wadi_scope | Resolve a .wdl's variables, points & grid lines to their actual values (with each variable's formula). See what main.x2 / House.W/2 resolves to before placing an object. | | wadi_preview | Render a .wdl to PNG images you can look at — floor plans, elevations, roof top view. Confirm layout/sizes/openings/roof visually. | | wadi_examples | List, or fetch the full source of, a validated example .wdl (minimal / two_room / two_story / coastal / complete). Copy from these. | | wadi_reference | The authoring docs, embedded: guide, dsl, conventions, coordinate-system, parametric-conventions, roof-v2-guide, data-model. | | wadi_view_3d | Load a .wdl into the running Wadi desktop app's live 3D view (so you + the user see the same model). Needs the app open. | | wadi_capture_3d | Render a .wdl in the running app and return a real 3D image (the textured model). Choose the shot with camera (a named exterior angle: iso/front/back/left/right/top) or room (first-person interior); isolate/layers show-only or toggle layers before the shot (by id or label). The response lists the house's layers so you can refine. Needs the app open. |

The last two reach the desktop app over a localhost bridge (127.0.0.1:8765, override WADI_APP_PORT); when the app isn't running they return a "open the Wadi app" message and you fall back to wadi_preview (headless 2D). The first four never need the app.

Run it

From a checkout (dev):

npm install
npm run dev          # stdio MCP server (gen-assets + tsx src/server.ts)

Self-contained bundle (no repo afterwards):

npm run build        # → dist/server.mjs (everything inlined except @resvg/resvg-js)

dist/server.mjs runs anywhere Node ≥20 is available, with only @resvg/resvg-js installed alongside it.

Register with an agent

Published to npm — zero install (nothing to build or clone; npx fetches on first run):

claude mcp add wadi -- npx -y wadi-mcp        # Claude Code

{ "mcpServers": { "wadi": { "command": "npx", "args": ["-y", "wadi-mcp"] } } }

From a local build (npm run build above) — point at the bundle by path:

{ "mcpServers": { "wadi": { "command": "node", "args": ["/abs/path/to/wadi-mcp/dist/server.mjs"] } } }

Any MCP client (Cursor, Windsurf, Claude Desktop, …) — use the same command + args (stdio transport). Then ask the agent to design a house; it calls wadi_reference('guide') to learn the workflow, wadi_examples to copy a starting point, and wadi_check / wadi_preview as it authors the .wdl.

The agent still writes a .wdl file you both co-edit; for the live 3D preview, open that file in the Wadi DSL editor (desktop ⌘⇧D, or https://wadi.house/dsl). This server provides the headless check + 2D image previews the agent reads on its own.

Verify

npm run smoke                              # in-process pipeline (check + render)
npx tsx scripts/client-test.mjs            # end-to-end over the MCP protocol
# no-repo proof: build, copy dist/server.mjs to a temp dir, `npm i @resvg/resvg-js`, then
npx tsx scripts/standalone-client.mjs <temp>/server.mjs

How it stays in sync

The server imports the real pipeline from editor/src and wadi-dsl/src (see src/pipeline.ts), so wadi_check/wadi_preview match the app byte-for-byte — there is no second implementation to drift. scripts/gen-assets.mjs re-embeds the examples and reference docs at build time. Rebuild (npm run build) after changing the schema, the DSL, the conventions, or the docs.

Publishing

npm publish (from wadi-mcp/). prepublishOnly runs build + smoke first, so the published tarball always contains a freshly-bundled, tested dist/server.mjs (the only files shipped are dist/ + package.json + this README). Bump version first.

The wadi_view_3d / wadi_capture_3d tools are backed by a localhost HTTP bridge the Tauri desktop app serves (src-tauri/src/lib.rs → /health, /load, /capture); the main window's viewer answers via a wadi://bridge-request listener that drives window.wadi.load + window.wadiCapture3D (editor/src/viewer/main.ts). Bound to 127.0.0.1 only.