Skip to main content
Glama
tvolodi

penpot-headless

by tvolodi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to penpot-headless

No user-submitted related servers found.

    Related Servers

    • Soma Nexus MCP

      pablostefan
      F
      license
      B
      quality
      D
      maintenance
      MCP server that fetches Figma data (file trees, nodes, images, components, styles, variables) and serves as a foundation for Flutter code generation.
      13
      -

    • Figma Local Bridge

      Miart
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      214 npm
      1
      MIT

    • Figma Local Bridge

      shaxaydev
      A
      license
      A
      quality
      C
      maintenance
      A 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.
      10
      214 npm
      1
      MIT

    • localfig

      LucasGorgal
      A
      license
      A
      quality
      B
      maintenance
      The Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.
      10
      47 npm
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 54 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources