Skip to main content
Glama
miguelcc06
by miguelcc06

Related Servers

Alternatives to front-design-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that indexes all projects on your machine and provides coding agents with briefings about each project's stack, services, and run instructions, so they can start sessions with context across all repos. No cloud, no accounts, no telemetry.
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.
      105 npm
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.
      74
      14 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.
      17 npm
      MIT
    • F
      license
      B
      quality
      A
      maintenance
      A local-first, agent-agnostic MCP server that provides semantic search, persistent memory, and automated code review capabilities for development workflows. It leverages the Auggie SDK to offer advanced tools for codebase indexing, implementation planning, and deterministic static analysis.
      52
      48
      -

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes: health checks separate liveness from readiness, and search vs browse vs find differ in mechanism. However, find_components overlaps somewhat with discover_frontend_resources, and compare/recommend/build are all advisory in nature, which could cause occasional misselection.

    Naming Consistency4/5

    All tool names are snake_case and follow a verb_noun pattern. Minor inconsistency: front_design_ping and front_design_health use the front_design_ prefix, while others place 'frontend' in the middle or end (e.g., discover_frontend_resources). Overall still predictable.

    Tool Count5/5

    10 tools is well-scoped for a frontend design knowledge and advisory server. Each tool covers a distinct part of the workflow: health, discovery, search, details, comparison, recommendation, and brief building. There's no bloat or thinness.

    Completeness4/5

    The server provides solid coverage for the core lifecycle of frontend design assistance: discover, search, retrieve details, compare, recommend, and build a brief. Minor gaps exist, such as missing an explicit way to list all available frameworks/categories or a dedicated 'list sources' endpoint, but these are not critical.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues