Skip to main content
Glama
akari2600

figma-developer-docs-mcp

by akari2600
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to figma-developer-docs-mcp

No user-submitted related servers found.

    Related Servers

    • figma-mcp

      Anakintano
      F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.
      5
      1
      -

    • Figma MCP Server

      AIYA861202
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Cursor to interact with Figma designs programmatically. Supports reading design information, modifying elements, creating components, managing text content, and automating design workflows through natural language commands.
      732 npm
      MIT

    • figmad-mcp

      toro1221
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.
      20
      -

    • figma-console-mcp

      Rydvansky
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.
      6,112 npm
      MIT

    • figma-mcp

      iflow-mcp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to access Figma files and prototypes, allowing them to retrieve design data and assets directly.
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one reads the index to discover available documentation, one reads specific pages for detailed content, and one searches across all documentation. There is no overlap in functionality, making it easy for an agent to select the right tool based on the task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with hyphens: 'read-figma-developer-docs-index', 'read-figma-developer-docs-pages', and 'search-figma-developer-docs'. This predictability enhances usability and reduces confusion.

    Tool Count4/5

    Three tools are well-scoped for the server's purpose of accessing Figma developer documentation, covering discovery, reading, and searching. While slightly minimal, each tool earns its place, and there is no bloat or obvious missing functionality for this focused domain.

    Completeness5/5

    The tool set provides complete coverage for the domain of accessing documentation: it allows agents to discover available docs via the index, read specific pages for detailed information, and search across all content when needed. There are no gaps that would cause agent failures in typical documentation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources