Skip to main content
Glama
multicomak

BrixUI MCP Server

by multicomak

Related Servers

Alternatives to BrixUI MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.
      5 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for design tokens that gives AI agents read access to design systems, enabling token resolution, listing, and component usage lookups via natural language.
      MIT
    • 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.
      18 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI coding agents access to Figma design data, enabling pixel-perfect implementation of designs through structured data extraction, image downloads, and design token retrieval.
      27 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: retrieving component details, design tokens, listing all components, and searching. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'verb_brix_noun' using snake_case, making the naming predictable and easy to remember.

    Tool Count3/5

    With only 4 tools, the server is quite minimal. While acceptable for a focused read-only surface, the count feels thin for a comprehensive design system interface.

    Completeness2/5

    The server only provides read operations (get, list, search). There are no tools for creating, updating, or deleting components or design tokens, leaving significant gaps for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues