penpot-headless
Related Servers
Alternatives to penpot-headless
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server that fetches Figma data (file trees, nodes, images, components, styles, variables) and serves as a foundation for Flutter code generation.13-
- AlicenseBqualityCmaintenanceBridges a local Figma development plugin to a local MCP server, letting the client read and write real canvas layers through the Figma Plugin API without consuming official MCP or Dev Mode quota. Supports layer and auto-layout editing, component and variable inspection, design-to-code context retrieval, and PNG/JPG/SVG/PDF export.21MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to drive the real Figma Desktop plugin API through one local daemon, so agents can read and edit the open file, take screenshots, export assets, and inspect variables, components, and styles. Everything stays on 127.0.0.1 with no cloud, API keys, or Dev/Full seat required.71 npm1MIT
- AlicenseAqualityCmaintenanceA local MCP server that reads and edits a Figma Design file through a development plugin, creating real editable layers (frames, text, shapes, components, images) rather than flattened screenshots. It runs entirely on loopback with no personal access token, API key, or cloud bridge, letting an agent inspect documents, build and update layers, export previews, and wire up prototype navigation.1071 npm1MIT
- AlicenseBqualityCmaintenanceLocal MCP server connecting AI clients to the Figma desktop app for inspecting and editing Figma documents via the Plugin API.1616 npm1MIT
- AlicenseNot gradedqualityDmaintenanceToken-efficient Figma MCP server with image export, query DSL, and design token support.4 npmMIT
TDQS
Scored across 54 tools
Each tool targets a distinct operation or entity (file, page, shape, component, comment, checkpoint, media, etc.), with no overlapping purposes. Even similar tools like penpot_add_shapes and penpot_add_component_instance are clearly differentiated by their descriptions.
All tools follow the penpot_{verb}_{noun(s)} pattern with imperative verbs (add, create, delete, get, list, update, etc.) and descriptive nouns. The naming is uniform and predictable across the entire set.
With 54 tools, the set is significantly larger than the typical well-scoped range of 3-15. While the breadth of Penpot's feature set may justify many tools, the sheer number makes it unwieldy for an agent and suggests the server could benefit from consolidation or higher-level operations.
The tool surface covers the full lifecycle for files, pages, shapes, components, variants, comments, and media, plus supportive utilities like checkpoints, text measurement, and batching. There are no obvious gaps for the domain of headless Penpot operations.