Connect Claude AI and other LLMs to Penpot designs via Model Context Protocol
If you already use Penpot MCP, the penpot mcp mcp server is the piece that lets your assistant work with it directly. Connect Claude AI and other LLMs to Penpot designs via Model Context Protocol.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Command — line Utilities**: Powerful CLI tools for design file analysis and validationlist_projects — List all Penpot projectsget_project_files — Get files for a specific projectget_file — Retrieve a Penpot file by its ID and cache itexport_object — Export a Penpot object as an imageget_object_tree — Get the object tree structure for a Penpot objectsearch_object — Search for objects within a Penpot file by namePrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — Create a .env file based on env.example with your Penpot credentials:Resources — The Resources tool exposed by this serverTools — The Tools tool exposed by this serverConfiguration is passed through the environment: PENPOT_API_URL, PENPOT_USERNAME, PENPOT_PASSWORD, YOUR_PROJECT_ID, YOUR_FILE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Penpot MCP's toolset — Command, list_projects, get_project_files and 11 more — is a fair guide to whether it matches your workflow. It is maintained by montevive; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Command | line Utilities**: Powerful CLI tools for design file analysis and validation |
| list_projects | List all Penpot projects |
| get_project_files | Get files for a specific project |
| get_file | Retrieve a Penpot file by its ID and cache it |
| export_object | Export a Penpot object as an image |
| get_object_tree | Get the object tree structure for a Penpot object |
| search_object | Search for objects within a Penpot file by name |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | Create a .env file based on env.example with your Penpot credentials: |
| Resources | The Resources tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
| Linting | The Linting tool exposed by this server. |
{
"mcpServers": {
"penpot": {
"command": "uvx",
"args": ["penpot-mcp"],
"env": {
"PENPOT_API_URL": "https://design.penpot.app/api",
"PENPOT_USERNAME": "your_penpot_username",
"PENPOT_PASSWORD": "your_penpot_password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PENPOT_API_URL | Endpoint or connection string the server talks to. | Yes |
| PENPOT_USERNAME | Configuration value read at startup. | Optional |
| PENPOT_PASSWORD | Configuration value read at startup. | Optional |
| YOUR_PROJECT_ID | Configuration value read at startup. | Optional |
| YOUR_FILE_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.