Skip to main content
Glama
chrissgon

perfectui-mcp

by chrissgon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to perfectui-mcp

No user-submitted related servers found.

    Related Servers

    • material-web-mcp

      shanthropic
      A
      license
      A
      quality
      C
      maintenance
      Provides programmatic access to Material Web documentation and components for AI agents, enabling documentation search, template generation, and HTML validation.
      7
      8 npm
      1
      MIT

    • Components Build MCP

      getlokiui
      A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with tools to grade, generate, and validate UI components against the components.build specification. Supports searching documentation, checking compliance, and generating framework-agnostic accessible components.
      11
      9 npm
      Apache 2.0

    • melta-ds-mcp

      tsubotax
      A
      license
      A
      quality
      A
      maintenance
      It lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.
      6
      364 npm
      201
      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 5 tools

    Disambiguation4/5

    get_install and get_component both retrieve documentation content for installation, but get_install is a specialized shortcut for install commands while get_component returns full Markdown of any document; descriptions clarify the boundary. Other tools (list_components, search_docs, check_markup) have clearly distinct purposes. Minor overlap prevents a perfect score.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_install, list_components, search_docs, get_component, check_markup). This makes the set predictable and easy to parse.

    Tool Count5/5

    Five tools cover the essential operations for a UI library documentation server: installation lookup, listing documents, searching, retrieving a document, and validating markup. Each tool has a clear role and the set is well-scoped.

    Completeness5/5

    The surface covers installation, discovery (list, search), retrieval, and validation, including legacy class migration. No obvious dead ends for the stated purpose of helping agents use Perfect UI correctly; the documentation lifecycle is fully covered.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources