Skip to main content
Glama
kkse7en

WorkBuddy Figma

by kkse7en
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to WorkBuddy Figma

No user-submitted related servers found.

    Related Servers

    • Local Figma MCP Bridge

      ikoba0911
      A
      license
      Not graded
      quality
      D
      maintenance
      Unofficial local MCP bridge for reading the currently open Figma file through a Figma plugin. Provides tools to inspect selection, file info, and export selected nodes as SVG/PNG.
      MIT

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      1
      MIT

    • Figma Bridge

      Clovis500c
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.
      43 npm
      3
      MIT

    • 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.
      206 npm
      1
      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

    B3.1/5.0

    Scored across 21 tools

    Disambiguation3/5

    The read surface has several overlapping tools — get_selection, get_metadata, get_design_context, get_screenshot, and get_figjam all inspect document state, and the distinctions rely on dense guidance like 'prefer summary for discovery' or 'bounded tree.' The descriptions do steer an agent, but misselection between get_metadata and get_design_context is plausible. The write/session/assets tools are clearly distinct.

    Naming Consistency4/5

    Nearly everything follows snake_case verb_noun (get_selection, list_fonts, download_assets, set_local_component_links), and the local/set_local pair signals read/write predictably. Minor deviations: a figma_ prefix on three tools and noun-first forms like get_figjam and get_screenshot.

    Tool Count3/5

    At 21 tools the surface is heavy for what is largely one domain (inspect + mutate a Figma doc), and several read tools could plausibly be collapsed. Each tool does have a defensible niche, so it's borderline rather than bloated.

    Completeness4/5

    Coverage spans document selection/session setup, deep reads (metadata, design context, components, variables, libraries, motion, FigJam), asset import/export, and arbitrary mutation via use_figma scripting, so no dead ends for typical workflows. Minor gaps: no first-class node create/delete/styling tools independent of scripting, and no published Code Connect operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources