wall-mcp
v0.1.1
Published
A wall of complete landing pages to compare, choose from, and hand back to your agent as a spec. Runs on the Claude you already have.
Maintainers
Readme
Wall
Choose the feeling you like.
Generating a page is solved. What nobody gives you is many at once, live, side by side — which is how design decisions are actually made. Wall's one act is compare and choose.
From your agent
One line, nothing else to install:
claude mcp add --scope user wall -- npx -y wall-mcpAsk for a landing page. Wall opens in your browser, you browse a wall of real pages, pick one, and the choice returns to your project as a spec your agent implements in your own stack — design tokens, structure, and copy, not a static file to port.
Nothing else to download: npx resolves the latest version on every run, so Windows and
Linux work without a build and a run is never stale. A desktop app is coming.
Three tools: design opens Wall and waits · collect reads a choice made after it
stopped waiting · check names the patterns that make a page look generated.
From a clone
npm install
npm run web # browser — the same code the MCP server opens
npm run serve # self-hosted; ANTHROPIC_API_KEY stays on the server
npm run app # the desktop shell, not released yetModel keys are optional. Layouts, variants, and export all run locally with no key; a key is used only for model-written copy, and it never leaves your machine.
What it does
- Forge twelve — six layout archetypes × your taste sheet, rendered as live pages, not screenshots. Instant, local, no template gallery.
- Taste from a screenshot — drop a page you love and Wall reads the design system out of it into an editable contract.
- Breed, don't prompt — pin two variants and the child takes one's layout and the other's typography.
- Ship a real file — a self-contained
index.htmlyou own: inlined CSS, no framework, no runtime of ours.
Docs
- Development notes — verification suites, streaming, slop detection, design worlds, server deployment
- Flows — every path through the app, and the code that carries it
- Architecture — the module map and the boundaries
- Landing page prompt — the brief for Wall's own page
- Original design doc — the first sketch, kept as a record
Verify everything with npm run verify:all — real browsers, recorded streams, no key
and no tokens spent.
MIT © Amin Khorramii
