mcp

What the MCP server does

The MCP server is the bridge between your Zaai Dev workspace and your coding agent. Your agent reads captures, palettes, HTML, structure, and brand briefs directly — no pasting screenshots.

How it works

@zaai-dev/mcp runs locally as a stdio MCP server. Your MCP client (Claude Code, Cursor, VS Code, and others) launches it on demand with npx; it authenticates to zaaidev.com with your token and exposes a set of read tools the agent can call.

  • Pull captures and their palette, HTML, animation, media, and structure.
  • Read brand briefs slice by slice — voice, audience, design intent, tokens, decisions.
  • Get a whole project in one call, or attach a single capture as a resource.

Set it up

  1. 1
    Mint an mcp token — see Authentication & tokens.
  2. 2
    Add the server to your client: Claude Code, Cursor, or VS Code & others.
  3. 3
    Ask your agent to list your captures or pull a brief — it'll call the tools automatically.

requirements

Node.js 20 or newer (node --version) and an mcp-kind token. Most tools cost 1 credit per call; health and whoami are free. See the tools reference for per-tool costs.