Quickstart

mcut project files are JSON documents. The fastest way to see the current shape is to create one with the CLI, summarize it, then apply edits through commands or operators.

Inspect the CLI

bunx @mcut/cli --help

The CLI runs outside the browser. It can scaffold, validate, summarize, lint, and batch-edit project files.

Create a project

bunx @mcut/cli new project.mcut.json
bunx @mcut/cli summarize project.mcut.json

Use summarize before and after edits. It gives the same compact view that MCP agents receive from get_summary.

Connect an MCP client to a project file

{
  "mcpServers": {
    "mcut": {
      "command": "bunx",
      "args": ["@mcut/mcp-server", "project.mcut.json"]
    }
  }
}

The stdio MCP server creates the project file when missing and rewrites it after successful edits.

Connect to a live browser editor

Use the live bridge when the browser tab should remain the source of truth:

bunx -p @mcut/mcp-server mcut-mcp-live --editor-url http://localhost:3000/editor

The command prints an editor URL with bridge query parameters and an MCP client configuration block. Keep the process running while the agent edits.

For lower-level local bridge control, use:

bunx -p @mcut/mcp-server mcut-bridge start --editor-url http://localhost:3000/editor
bunx -p @mcut/mcp-server mcut-bridge mcp

Next steps

• Read Project model before editing JSON directly.
• Use commands for exact project mutations.
• Use operators for UI-like editing actions.
• Use SDK Reference for exact TypeScript exports.