Skip to main content
Glama
Sign In
ComponentPilot MCP

ComponentPilot MCP

by Sricharan-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ComponentPilot MCP

No user-submitted related servers found.

    Related Servers

    • Tessera

      radityama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to search, inspect, and retrieve real UI components from existing component libraries, with ranked results, score explanations, licence and provenance details, and safe installation plans. It also surfaces similar components and higher-level UI patterns so agents can reuse existing interface code instead of generating it from scratch.
      34 npm
      MIT

    • Niblet

      NaoMikhailov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to find real UI screen references and design materials, retrieve recorded design-system details for selected screens, and diagnose catalog access while building product UI.
      MIT

    • Inspo MCP

      Nutlope
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to search and retrieve real production websites, their design systems, and reference components over MCP, so they can study design patterns before writing UI.
      982
      MIT

    • kodza

      kodza-dev
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.
      2
      2
      -

    • ui2vibe-mcp

      KR-PRO-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.
      MIT

    • Niblet

      tRamos37
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to ground UI work in real product screens by searching a catalogue for concrete screen references and design materials such as fonts, icons, and animated icons, then pulling the colors, typography, components, and provenance behind a chosen web screen. It also serves bundled skill documents, command playbooks, and connection diagnostics so an agent can settle a screen's states and acceptance criteria before building and verify the rendered result afterward.
      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

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: discovery (find_components, find_design_systems), content retrieval (get_component_examples, get_accessibility_guidance), comparison, demo inspection, and health. The closest overlap is between get_component_examples, compare_implementations, and inspect_component_demo, since all deal with source-linked implementations, but descriptions and the explicit queue/poll pairing of inspect_component_demo and get_component_demo_run keep boundaries reasonably clear.

    Naming Consistency4/5

    The set overwhelmingly follows a consistent verb_noun snake_case pattern (find_components, get_component_examples, compare_implementations, inspect_component_demo, get_component_demo_run). The only minor deviation is health_check, a conventional noun-first name, but it is immediately readable and does not disrupt the pattern.

    Tool Count5/5

    Eight tools is well-scoped for a component discovery and demo-inspection server. Each tool maps to a distinct workflow step: discovery, examples, design systems, accessibility, comparison, demo queueing, demo retrieval, and health.

    Completeness4/5

    The surface covers the main lifecycle from component discovery through examples, comparison, and bounded demo inspection, plus design-system search and accessibility guidance. Minor gaps remain: there is no direct tool for retrieving a single component's metadata/details, and design-system search lacks a corresponding detail/retrieval operation.

    Resources