MCP server

Penpot MCP

Penpot MCP is the official server that lets an AI client read and edit your Penpot designs, from renaming layers to drafting HTML and CSS.

Run
npx -y @penpot/mcp@latest
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is Penpot MCP?

Penpot MCP is Penpot's official Model Context Protocol server. It lets an AI client such as Cursor or another MCP client read a design file and change it by running code through Penpot's plugin API. You can use the hosted server from your Penpot account or run it locally with Node.js.

Penpot MCP is the official Model Context Protocol server for Penpot, the open-source design tool. It gives an AI client a way to inspect your open design file and to change it, so the agent works on your real components and styles.

The server exposes tools to the client. A Penpot plugin running in your open browser tab connects that file to the server over WebSocket. The agent then writes and runs code snippets through Penpot's plugin API.

The code is MPL-2.0. Development now lives in the mcp folder of the main Penpot repository, and the older penpot/penpot-mcp repository points there.

What it changes in your workflow

  • Design system upkeep. Create spacing, type and colour tokens, rename layers to a scheme, organise components and audit styles for redundancy.
  • Broad edits. Apply a palette update across a whole file or generate component variants.
  • Design to code. Extract layout structure, inspect tokens and generate semantic, modular HTML and CSS from a design.
  • Asset export. Pull out only the icons a file uses.
  • New screens. Draft screens from an existing design system.

Because the agent reads your real file, it starts from your own tokens and components instead of inventing a style.

Who it is for

  • Designers who maintain a design system in Penpot and want the dull maintenance done by an agent.
  • Developers who want exact values from a file instead of guessing a hex code from a screenshot.
  • Teams who prefer a hosted setup with nothing to install.

Who it is not for

  • Anyone expecting a one-click Penpot to WordPress export. The server stops at the design.
  • Setups that rely on a weak model. Penpot says weaker models, including most locally hosted ones, are unlikely to give usable results beyond simple tasks.
  • Workflows where the Penpot tab cannot stay open, because the plugin runs inside it.

Hosted or local Penpot MCP

HostedLocal
InstallNone. Enable it in your Penpot accountNode.js 20 or later, then npx -y @penpot/mcp@latest
AuthPersonal MCP key inside the server URLPlugin loaded from localhost, no key
Local filesNo. import_image from local paths is unavailableYes
Best forWorking on designs onlyCoding tasks that need files on disk

Use it with UiChemy

Penpot MCP does not publish to WordPress, and UiChemy lists no Penpot import. The route that holds is code. Have the agent write a section as HTML and CSS, preview it at a URL, then bring that build into WordPress with UiChemy AI to WordPress. For the Figma side of the same idea, see Figma Make vs Lovable.

Pair the agent with the frontend-design skill if you want a design plan before it writes code. For the WordPress end, Lovable to Elementor walks through an import with UiChemy AI to WordPress.

Want the WordPress end of that route? Get Started with UiChemy.