Skip to main content
Glama
Fupete

Filo

by Fupete
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Filo

No user-submitted related servers found.

    Related Servers

    • @dsk/mcp

      rabindranath1311
      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

    • ds-mcp

      aestheticfunction
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.
      6 npm
      1
      Apache 2.0

    • uiverse-mcp

      Fabi-SPL
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Uiverse.io that lets AI agents browse, search, and fetch open-source UI components (HTML + CSS) directly in their editor. No API key required, it indexes 3,800+ components locally.
      8
      7
      1
      Apache 2.0

    • bunge-ds-mcp

      tabaldi98
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes the @bunge/ds-components design system catalog, allowing AI assistants to list, search, and retrieve component details including inputs, outputs, usage examples, and import instructions.
      4
      MIT

    • ds-pilot

      lyse-labs
      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
    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.3/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: token tools cover list/resolve/search/find, component tools cover inventory/variants/markup/props, and docs/GitHub tools are separated. The only potential overlap (dsi_list_components vs. bsi_list_components_by_status) is differentiated by scope, so agents can reliably choose the right tool.

    Naming Consistency4/5

    Most tools follow a [domain]_[verb]_[entity] pattern (e.g., tokens_list_component_vars, bsi_get_component_markup, github_get_component_issues) with consistent use of list/get/search. Minor deviations like 'ping' and 'tokens_search' (missing explicit object) slightly break the pattern, but the convention remains predictable.

    Tool Count4/5

    At 17 tools, the server is slightly above the typical 3-15 range, but the breadth is justified by the many facets of the design system (tokens, components, variants, markup, props, docs, issues). The tools are tightly scoped to read-only information retrieval, so the count feels reasonable rather than excessive.

    Completeness5/5

    The tool set comprehensively covers the domain: you can discover components, list/search tokens, resolve variables, fetch variants and markup for both libraries, get props for Dev Kit components, access usage docs, and link to GitHub issues. There are no dead ends—any component found can be further explored through the available tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources