Skip to main content
Glama
Carnegie Mellon Web Kilt MCP Server

Carnegie Mellon Web Kilt MCP Server

Official
by cmu-web

Related Servers

Alternatives to Carnegie Mellon Web Kilt MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to build UI with a design system's tokens, component inventory and prop signatures, page templates, and starter snippets, while tracking free/pro availability and live-updating design data.
      11
      102 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and ask questions across versioned service documentation, retrieve documents and diffs, and find related docs with cited answers over Streamable HTTP, SSE, or stdio.
      242 npm
      MIT
    • A
      license
      A
      quality
      B
      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
      272 npm
      202
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives coding agents real product screen references, fonts, icons, and recorded design-system details so UI can be built from an actual catalogue instead of a generic template. It also serves bundled design-workflow resources, prompts, and connection diagnostics, optionally without any token.
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action on a distinct object: search_components lists matches, get_component retrieves one component's details, get_install returns setup code, get_conventions returns rules, and check_html validates markup. There is no meaningful overlap between listing, fetching, and validating.

    Naming Consistency5/5

    All five tools use a consistent snake_case verb_noun pattern (search_, get_, check_). The verbs accurately reflect the action, and there is no mixing of conventions.

    Tool Count4/5

    Five tools is on the low end but covers the discover/read/install/validate lifecycle without redundancy. Slightly more surface (e.g., a separate token or template lookup) could exist, but nothing feels extraneous.

    Completeness4/5

    The surface covers finding components, reading their docs, installing the kit, retrieving conventions, and validating HTML—the core workflows for building a page with this kit. Minor gaps remain, such as retrieving full page templates or searching within the conventions, but agents can work around these.