Penpot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PENPOT_API_URL | No | API base URL (defaults to https://design.penpot.app/api) | https://design.penpot.app/api |
| PENPOT_ACCESS_TOKEN | Yes | Your Penpot access token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_boardB | Retrieves a Penpot board and converts it to Tailwind CSS code |
| debug_boardA | Retrieves a Penpot board and displays raw JSON for debugging |
| get_tokensA | Retrieves design tokens from a Penpot file and formats them according to DTCG standard |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: debug_board returns raw JSON, get_board converts to Tailwind CSS, and get_tokens retrieves design tokens. No ambiguity between them.
All tool names follow verb_noun pattern (debug_board, get_board, get_tokens), but one uses 'debug' while the other two use 'get', showing slight inconsistency in verb choice.
Three tools is on the lower side but still reasonable for a focused server. It covers core retrieval operations without being overly minimal.
The tool surface covers board retrieval and token extraction but lacks operations like listing files, projects, or creating/updating content, which are notable gaps for a design server.