Open Builder CLI
CLI and local MCP server for web projects: templates, design systems, static checks and verification scripts.
- 110 ★ on the repository
- Last commit
- GPL-3.0
Extended access
Why this level
- Creates files in the workspace and, with `--allow-project-scripts`, runs project scripts on your machine.
Install
- Works in
Manual install
npm install -g ./artifacts/headless/open-builder-cli-0.1.0.tgzBuild the archive first with `pnpm install` and `pnpm headless:pack`. Node.js 24 is required.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates files in the workspace and, with `--allow-project-scripts`, runs project scripts on your machine.
This is third-party code. Review the repository files before installing.
What it does
The `@open-builder/cli` package in the Open Builder repository gives an agent native tools for frontend projects. It creates a project from the `react-ts` (React, TypeScript, Vite) or `static` (HTML, CSS, JavaScript) template, applies one of the reference design systems (`linear`, `stripe`, `notion`) and checks the project statically. `open-builder verify` runs an existing project script: build, typecheck, lint or tests. The same set works as a local MCP server, `open-builder mcp --stdio`, with the tools `builder_list_templates`, `builder_init_project`, `builder_apply_design_system`, `builder_check_project` and `builder_verify_project`. Source code, dependencies and browser verification stay with your own agent.
Who it is for. Developers who have Claude Code or Codex build a frontend project and want starters, design references and checks.
Good fit when
- An agent needs a clean starter on React and Vite or plain HTML.
- The interface should approach a reference system, for example in the style of Linear or Notion.
- You need a static project check with exit codes for CI.
- Verification scripts are allowed to run only behind an explicit flag.
Not a fit when
- You need a web builder with live preview; that belongs to Open Builder itself, not the CLI.
- The environment cannot provide Node.js 24.
- You need browser behavior and accessibility checks; static checks do not cover them.
Example request
Create `./demo` from the react-ts template in the notion style, then check it with the check command and run build.Limitations
The package is built from the repository source with `pnpm install` and `pnpm headless:pack`, then installed from a local archive; the author treats an npm registry release as a separate action. Node.js 24 is required and the license is GPL-3.0. Static checks report what they skipped and do not prove compilation, browser behavior, accessibility or visual quality. `verify` accepts only `build`, `typecheck`, `lint` and `test` as existing project scripts and uses the installed package manager. Reference designs are unofficial and ship without brand assets. Verification is off in MCP until `--allow-project-scripts` is passed.
How to disable. Remove the package with `npm uninstall -g @open-builder/cli` and delete the `open-builder` entry from the agent's MCP settings.
FAQ
How do I install Open Builder CLI?
From a clone run `pnpm install`, `pnpm headless:pack` and `npm install -g ./artifacts/headless/open-builder-cli-0.1.0.tgz`. The npm registry is not used yet.
Which templates and designs exist?
Templates `react-ts` and `static`. Reference visual systems `linear`, `stripe` and `notion`. `open-builder templates list --json` and `open-builder design list --json` list them.
How do I start the MCP server?
With `open-builder mcp --stdio --root /absolute/workspace`. The workspace root is fixed at startup and tool paths stay relative.
How do I enable script verification in MCP?
Add the startup flag `--allow-project-scripts`. Tool arguments cannot enable it; the decision is made only when the server starts.
What are the CLI exit codes?
0 for success, 1 for findings or a failed task, 2 for invalid or missing configuration, 124 on timeout and 130 on cancellation.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CodeRocket MCP server gives an agent a saved library's design rules, components and blocks over a read-only connection.
Angular’s official CLI creates application workspaces, starts development servers and supports ongoing project maintenance.
Rockpack Starter is a React CLI with app and library templates built around TypeScript and extensible Webpack configuration.
Ignite UI CLI scaffolds Angular, React and Web Components projects, and ig ai-config sets up MCP servers and skills.
A design studio for people and agents: dsa CLI, MCP endpoint and skill to edit layouts, slides, reports and 3D together.
The Catalyst framework MCP server: the agent gets project knowledge, explains errors, checks config and follows a conversion plan
README in short
The CLI scaffolds a project, applies a design and checks the result with no model and no network, while the MCP server exposes the same to agents.