Penpot MCP

Why it's ranked here

The architecture supports unusually broad design automation because the agent can execute code against Penpot’s Plugin API instead of relying only on a narrow command set. Shared TypeScript contracts, correlated task responses, timeouts, and structured errors strengthen the bridge. However, setup has several moving parts, remote multi-user operation remains unfinished, and active development moved into Penpot’s main repository.

What's good

It covers retrieval, transformation, and creation rather than stopping at read-only inspection. Streamable HTTP serves modern MCP clients, while legacy SSE and an external proxy accommodate older client transports. Shared request and response types keep the server-plugin protocol consistent. Environment settings cover addresses, ports, logging, and remote mode. A browser REPL also supports direct experimentation with plugin code.

Tradeoffs

Users must run two servers, load a development plugin URL, keep the plugin window open, and manually connect it. Browser private-network rules can block localhost access or require explicit permission. Clients limited to standard input and output need an extra proxy. The agent may execute arbitrary code inside the plugin environment, which demands careful trust boundaries. Multi-user mode is testing-only, uses a hard-coded token, and cannot support local-file import or export tools.

How to use it well

Use it when an engineer or designer wants an AI client to inspect and programmatically reshape an active Penpot document, especially for design-to-design or code-to-design experiments. Start locally with a modern HTTP-capable MCP client, keep the plugin interface open, and review generated operations before trusting them. It does not replace production authentication, mature shared hosting, or remote file import and export infrastructure.

Observed

Primary language

Core server, shared protocol, and plugin components are written in TypeScript; Python scripts prepare development data.

Packaging

Private npm monorepo with coordinated install, build, start, formatting, and bootstrap scripts.

Interfaces

MCP over Streamable HTTP and legacy SSE, plus WebSocket communication between server and Penpot plugin.

Runtime

Requires Node.js and was tested with Node.js 22.

Client compatibility

HTTP-capable MCP clients connect directly; stdio-only clients require an external proxy.

Repository status

The standalone repository is archived, with its contents integrated into the main Penpot repository.

Structure

Monorepo contains shared types, an MCP server, a Penpot plugin, and Python development helpers.