Penpot MCP Server

The architecture is the thing to understand before installing it. There is no REST call to a design file; the server keeps a WebSocket connection to a Penpot plugin loaded in the browser, and the model writes code against the Penpot Plugin API which then executes inside that plugin sandbox. Two consequences follow directly. The file has to be open and the plugin UI has to stay open, because closing it drops the connection. And the model is not restricted to a fixed set of design operations, since it composes plugin API calls itself. The server listens on a local port with a streamable HTTP endpoint and a legacy SSE one, and the repository carries both the server and the plugin.