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 the editor in Studio

Use the live bridge when the open editor should remain the source of truth. Install Studio, open it, and choose Add to Cursor or Copy MCP URL from the MCP menu. The URL is http://127.0.0.1:44737/mcp?token=<token>, see Connect Cursor.

For a stdio only client, expose the running app's bridge as a stdio server:

MCUT_BRIDGE_TOKEN=<token> bunx -p @mcut/mcp-server mcut-bridge mcp --port 44737

Developers who run the editor as a browser tab start the bridge themselves with mcut-mcp-live or mcut-bridge start, see the local bridge reference.

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.