Skip to main content
Glama
RomkaSk

Paragon MCP Server

by RomkaSk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Paragon MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • @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-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.
      3 npm
      9
      MIT

    • systembridge-mcp

      teyepe
      A
      license
      A
      quality
      C
      maintenance
      MCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.
      37
      8 npm
      2
      MIT

    • @sorb/tap

      metatoy
      A
      license
      Not graded
      quality
      B
      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.
      Apache 2.0
    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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation2/5

    get_component aggregates props, events, examples, and CSS variables, making the separate tools like get_component_props and get_component_events redundant and ambiguous. An agent may struggle to decide whether to use the general or specific tool, though the list/detail distinction for examples is clear.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern using get_ and list_. The only inconsistency is get_components_variables using plural 'components' while others use singular 'component'. Overall, the naming is predictable and readable.

    Tool Count5/5

    Seven tools is well within the ideal range for a component documentation server. Each tool addresses a legitimate aspect of component exploration, and the count feels appropriately scoped without being bloated.

    Completeness5/5

    The server provides a complete surface for exploring Paragon components: listing components, getting detailed info, and accessing props, events, CSS variables, and examples. No obvious gaps exist for the intended purpose of discovering component APIs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources