Skip to main content
Glama
Anguraj-zoho

Elegant MCP Server

by Anguraj-zoho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Elegant MCP Server

No user-submitted related servers found.

    Related Servers

    • coss-ui-mcp

      Zoot01
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the coss ui design system, enabling AI agents to fetch components, props, and design tokens on demand for accurate, low-cost code generation.
      6
      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

    • my-design MCP Server

      Davont
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI to interact with the private 'my-design' React component library and design tokens for UI generation and technical support. It provides tools for component searching, API documentation retrieval, and migration guidance based on specific internal design specifications.
      6
      -
    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/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: e.g., `get_component` returns HTML snippets, `get_full_wiki_file` returns full wiki content, `get_recipe` provides shell structure, and `get_shell` provides a skeleton. There is no overlap or ambiguity among the tools.

    Naming Consistency4/5

    Most tools follow a consistent `get_` prefix pattern (e.g., get_anti_patterns, get_chart_snippet). However, a few tools like `list_components`, `search_wiki`, and `setup_project` deviate, introducing minor inconsistency while still being readable.

    Tool Count5/5

    With 14 tools, the set is well-scoped for a domain focused on building pages with Elegant components. Each tool addresses a specific need without redundancy, and the count falls comfortably within the optimal 3-15 range.

    Completeness5/5

    The tool surface covers the full workflow for building pages: setup, anti-patterns, components, recipes, shells, charts, icons, screenshots, wiki search, and page blueprints. There are no obvious gaps; it provides everything needed to construct a page correctly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources