Code MCP Introduction
Code MCP runs a local, read-only MCP server on your machine so that AI coding agents — Claude Code, Codex, Cursor, VS Code, Antigravity, and others — can turn a finished ProtoPie prototype into real code.
Unlike Studio MCP, Code MCP is link-based: you point your agent at a ProtoPie Cloud link — a Pie's URL or one copied from Dev View — and it reads exactly the Pie and revision that link points to, pulling the scenes, layers, components, variables, and trigger–response interactions it needs. It runs locally via npx and talks to ProtoPie Cloud with your own account permissions over OAuth.
What you can do
Implement a whole prototype — or one scene, component, or layer — in your framework (React, SwiftUI, Compose, Flutter, QML, ArkTS) from a single link.
Inspect structure and behavior: the scene/layer tree, components, variables, and the interactions, conditions, and formulas behind them.
Pull original assets (images, fonts, thumbnails) so generated code keeps full visual fidelity.
Requirements
Node.js 20 or later.
A ProtoPie Cloud account with download access to the Pie (see Access and permissions).
A supported MCP client: Claude Code, Codex, Cursor, VS Code, Antigravity, or any other MCP-capable agent.
What it doesn't do
Converts
.pie→ code only; it doesn't turn code back into a.pie.Hands your agent an accurate spec, but final code quality depends on your agent and prompts.
Local (stdio) server only — no remote server yet.