faux-studio

Local MCP server that connects AI clients to Figma Desktop. Design with natural language — create components, manage tokens, and build production-quality layouts.

Quick Start

npx faux-studio

On first run, a browser window opens for Figma OAuth. After authentication, the server starts and your AI client can call Figma tools.

Configure Your AI Client

Claude Code

claude mcp add --scope user faux-studio -- npx faux-studio@latest

Or manually add to your MCP settings:

{
  "mcpServers": {
    "faux-studio": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "faux-studio"]
    }
  }
}

OpenCode

manually add to your MCP settings (~/.config/opencode/opencode.json):

{
  "mcp": {
    "faux-studio": {
      "type": "local",
      "command": [
        "npx",
        "faux-studio@latest"
      ]
    }
  }
}

Codex

codex mcp add faux-studio -- npx -y faux-studio@latest

Or manually add to your MCP settings (~/.codex/config.toml):

[mcp_servers.faux-studio]
command = "npx"
args = ["-y", "faux-studio@latest"]

How It Works

faux-studio runs locally and bridges your AI client to Figma Desktop:

1. AI client sends MCP tool calls (e.g., create_component, set_variable)
2. faux-studio generates Figma Plugin API scripts via the Faux cloud
3. Scripts execute in Figma via CDP (Chrome DevTools Protocol) or the Faux plugin

Requirements

• Node.js 20+
• Figma Desktop (running)
• Faux account (created on first auth)

Environment Variables

| Variable | Description | |----------|-------------| | FAUX_TRANSPORT | Force transport: cdp or plugin |

Links

• Website: faux.design
• Setup guide: faux.design/docs/setup
• Issues: github.com/Faux-Technologies/faux-studio/issues

Publishing a New Version

To publish a new version to npm:

1. Bump the version in package.json:

   npm version patch   # 0.4.0 → 0.4.1
   npm version minor   # 0.4.0 → 0.5.0
   npm version major   # 0.4.0 → 1.0.0

   This updates package.json and creates a git commit + tag automatically.

2. Push the commit and tag:

   git push && git push --tags

3. The publish workflow will build and publish to npm automatically on any v* tag push.

Note: Ensure the NPM_TOKEN secret is configured in the repo's GitHub Settings → Secrets and variables → Actions.

License

MIT