Penpot's MCP server lets LLMs edit design files directly

What it does

Penpot’s MCP server is a bridge that exposes design file data to LLMs and allows them to modify or create elements. It pairs an MCP server with a dedicated Penpot plugin; the two communicate over WebSocket so the LLM can execute code inside the Penpot environment. In short, it gives an AI client a scripting remote control for vector graphics.

The interesting bit

Most MCP servers stop at fetching data, but this one lets the LLM write and run arbitrary code snippets within the Penpot plugin sandbox to accomplish tasks. The model is not merely reading your layout—it is actively manipulating shapes and structures through Penpot’s own API.

Key highlights

• Monorepo containing the MCP server, the companion Penpot plugin, shared TypeScript definitions, and Python helper scripts
• Supports both modern Streamable HTTP and legacy SSE endpoints for connecting MCP clients
• Can run fully local or be configured for remote deployment; multi-user mode is documented but still in development
• The README states this repository was archived on 2026-02-03 and its contents merged into the main Penpot codebase

Caveats

• Requires running two separate servers and manually loading a plugin inside Penpot, plus dealing with browser private-network access restrictions for local connections
• Active development has moved to the main Penpot repository, so this standalone repo is frozen
• Remote multi-user support is described as work-in-progress

Verdict

Useful if you are building agentic workflows that need to edit design files programmatically, but consult the main Penpot repository for the current code. Avoid if you want a managed service—this is a self-hosted, two-part system that needs manual wiring.