Penpot MCP Server
Design file data queries, element creation, and transformation within Penpot environments.
Data last scanned today · Reviewed today
Overview
The Penpot MCP Server provides an integration layer that allows Large Language Models to interact with Penpot design files. It functions by utilizing a dedicated Penpot MCP Plugin, which connects to the server via WebSocket to execute code snippets directly within the Penpot Plugin API environment. This architecture enables LLMs to perform various operations, including the retrieval of design data, modification of elements, and the creation of new design components. Users are required to run both the MCP server and a separate plugin web server, then establish a connection within the Penpot interface.
Our verdict
With a security score of 39/100, this project is considered high risk. The repository has been officially archived since February 2026, with instructions to use the implementation now integrated into the main Penpot repository. Additionally, the security of its authentication methods and read-only mode have not been editorially reviewed, making it unsuitable for sensitive production environments.
- Integrated directly into the main Penpot repository
- Uses a small supply chain with only 2 direct dependencies
- Provides documented instructions for plugin connectivity
- Repository is archived and no longer maintained
- Authentication and read-only mode support remain unreviewed
- Last commit was over 130 days ago
Setup
{
"mcpServers": {
"penpot-mcp": {
"args": [
"-y",
"penpot-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Is this repository currently active?
No, this repository has been archived as of February 3, 2026, and its contents have been integrated into the main Penpot repository.
›What are the hardware or software prerequisites for running the server?
The project requires Node.js, and it is tested specifically with version 22.
›Are there specific browser requirements for the connection?
Chromium-based browsers have Private Network Access restrictions that may require you to approve local network requests or disable security shields, such as those in Brave, to connect to the plugin.
›Can I connect an MCP client that only supports stdio transport?
Yes, but you must use a proxy like mcp-remote to bridge the stdio transport to the server's HTTP/SSE endpoints.
›What happens if I close the plugin UI in Penpot?
Closing the plugin UI will terminate the connection to the MCP server, so it must remain open while in use.
›How does the LLM interact with my design files?
The MCP server communicates with a dedicated Penpot MCP Plugin via WebSocket, allowing the LLM to execute arbitrary code snippets within the Penpot Plugin API environment.
Alternatives
Badge
Maintain this server? Add the live badge to your README.