{"id":"io.github.ChanMeng666/archlang-mcp","slug":"io-github-chanmeng666-archlang-mcp","title":"ArchLang","description":"Floor plans as code: compile, lint and repair ArchLang (.arch) floor plans to SVG, DXF and PDF.","version":"0.2.48","publisher":{"kind":"github","id":"ChanMeng666","label":"@ChanMeng666 on GitHub","url":"https://github.com/ChanMeng666"},"website":"https://archlang.uk","repository":"https://github.com/ChanMeng666/archlang","remotes":[{"type":"streamable-http","url":"https://mcp.archlang.uk/mcp"}],"packages":[{"registryType":"npm","registryBaseUrl":"https://registry.npmjs.org","identifier":"@chanmeng666/archlang-mcp","version":"0.2.48","runtimeHint":"npx","transport":{"type":"stdio"}}],"published":"2026-11-19","updated":"2026-11-19","status":"online","auth":"","latency_ms":1567,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"compile","title":"Compile a floor plan to a drawing","description":"Compile ArchLang `.arch` source (or a Plan-JSON object) to an SVG floor plan, or with `format` to a plain-text ASCII plan (\"txt\"), Plan JSON (\"json\") or an image (\"png\"). Format \"json\" returns the plan as an object, with `schema` naming its JSON Schema; passed back as `plan_json` it compiles to the same drawing, unless the plan uses a part of the language Plan JSON does not carry (sheet tables, st","read_only":true},{"name":"describe","title":"Describe a plan (facts, no render)","description":"Report a plan's facts without rendering, so you can check it against the brief without looking at an image. Returns rooms (`area_m2`, measured on the wall centrelines; `net_area_m2`, the floor no wall stands on, absent when it cannot be computed exactly; bbox, adjacency, use, and the exact shape: `floor_polygon` for a `room polygon`, `floor_circle` for a `room circle`, whose area is exactly πR²), ","read_only":true},{"name":"lint","title":"Lint architectural soundness","description":"List advisory architectural-soundness warnings (`W_*` codes) as data: unreachable room, windowless bedroom, too-narrow door, blocked doorway, furniture through a wall, circuitous path, and more. `profile` selects a ruleset (\"residential-basic\", \"accessibility-advisory\", …).","read_only":true},{"name":"validate","title":"Validate (parse + resolve + lint)","description":"Check a plan in one pass without returning a drawing (parse, resolve and lint): the gate a plan passes before it ships. `strict:true` makes advisory warnings fail too. Optional `graph` checks the plan's interior-door adjacency against an intended room graph (`{ room: [neighbours] }`); a mismatch fails. Optional `intent` (a brief's expectations, shaped as the `archlang://intent-schema` resource des","read_only":true},{"name":"score","title":"Score a plan against a brief (intent meter)","description":"Measure how much of a brief's intent JSON a plan satisfies, without gating. Returns { ok, satisfied, total, score, subscores, violations }, where `score` is satisfied/total in [0,1] (an empty intent scores 1); call it across edits to watch a plan approach the brief. The intent's shape is the `archlang://intent-schema` resource. A malformed intent returns `{ ok:false, intentErrors }` as data, never","read_only":true},{"name":"repair","title":"Repair furniture placement","description":"Correct furniture placement and return the corrected `.arch` source with a change log. It pushes furniture out of walls, doorways and door swings, separates overlapping pieces, moves fixtures that sit in the wrong room, and snaps floating pieces to walls. A piece it may not rewrite is listed in `unresolved` with the reason. It never adds doors or windows (that is a design choice); use `suggest` fo","read_only":true},{"name":"fix","title":"Apply machine-applicable diagnostic fixes","description":"Apply the machine-applicable fixes attached to a plan's compile diagnostics and return the edited source. It corrects source-level faults (an opening off its wall becomes the attachment form, an out-of-range position is clamped, …); furniture geometry is `repair`'s job. It runs at most 4 passes and rolls back a pass that raises the error count. `unsafe:true` also applies `maybe-incorrect` fixes. R","read_only":true},{"name":"finish","title":"Finish the drawing","description":"Complete a plan for export by adding what it lacks; run it once `lint` is clean. Two stages. `furnish` puts furniture, by room use, in each rectangular room that holds none, on every storey (a furnished room is never touched, and one that lacks a piece its use requires is named in `unresolved` with the missing pieces, not filled; placement is `against wall` / `in <room> anchor`, never absolute). `","read_only":true},{"name":"suggest","title":"Suggest topology fixes (advisory)","description":"Suggest the doors and windows a plan's room graph needs, as data; nothing is applied. For a room with no path back, a building with no entrance, a bath reachable only through a bedroom, or a windowless bedroom, it returns ready-to-paste `door`/`window` statements with a rationale, for you to choose among and insert. Each names its wall by an authored id or a unique wall category, else by absolute ","read_only":true},{"name":"complete","title":"Completions at a source offset","description":"List the completion items in scope at a source byte offset: keywords, element names, ids and enum values, the same items an editor's language server offers. For structured or assisted authoring.","read_only":true},{"name":"explain","title":"Explain a diagnostic code","description":"Look up an E_/W_ diagnostic code in the catalogue: what it means, why it is raised and how to resolve it, with an example that raises it and, for most codes when the installed core has them, `fixed`, the same example corrected. Returns { ok:true, code, entry: { code, severity, message, cause, fix, example, fixed? } }, the `explain --json` of the CLI; an unknown code returns { ok:false, code }. The","read_only":true},{"name":"link","title":"Share link to the rendered plan","description":"Make two URLs that show a plan in the browser with nothing to install, for handing to a person. `playground` opens it in the hosted editor, rendered; `embed` draws it alone, for an iframe. The plan travels inside the URL, after the `#`, so it is never sent to a server and the URL carries nothing else. A plan that does not compile still gets links, and the page shows its diagnostics; `ok` says whet","read_only":true},{"name":"read_me","title":"How to use this server","description":"Explain this hosted ArchLang server in one short page: the authoring loop, the size cap, what is unavailable here, how to get an image URL for a plan, and what the server keeps (nothing). Call it first when unsure.","read_only":true}],"server_info":{"name":"archlang","version":"0.1.0"},"category":"developer","tags":["productivity"],"kind":"remote","source":"registry","submitted":{},"first_party":false,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-07-10","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/io-github-chanmeng666-archlang-mcp/"}