Skip to main content
Glama
laivannha0202

figma-opencode-mcp

by laivannha0202
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-opencode-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      73 npm
      1
      MIT

    • figma-bridge-mcp

      KaiUweHella
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.
      12
      30 npm
      1
      MIT

    • figma-mcp-rust

      alvinindra
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.
      52
      MIT

    • Figma Agent MCP

      TrungLee003
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that connects AI clients to Figma via a WebSocket bridge and native plugin, enabling deterministic design operations like inspection, creation, mutation, styling, validation, and optimization.
      14 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ping for health, getters for page/selection/tree, creators for frame/text, audit for design issues, and export for JSON. No overlap.

    Naming Consistency5/5

    All tools follow a consistent 'figma_verb_noun' snake_case pattern, making them predictable and easy to navigate.

    Tool Count5/5

    8 tools is well-scoped for a Figma design assistant, covering essential reading, creation, auditing, and health checking without being excessive.

    Completeness3/5

    Missing update/delete operations for nodes, lack of shape variety (only frame and text), and no style manipulation tools, leaving notable gaps for full design workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources