Skip to main content
Glama
Sign In
figma-opencode-mcp

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
      76 npm
      2
      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
      16 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
      527 npm
      1
      MIT

    • figma-mcp-rust

      alvinindra
      A
      license
      Not graded
      quality
      B
      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.
      78
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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 recent community issues

    Resources