Skip to main content
Glama
calebsjames

Atlas UI

by calebsjames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Atlas UI

No user-submitted related servers found.

    Related Servers

    • Component Library MCP

      vasyl-bilous
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that scans React and Vue projects, extracts component metadata (props, slots, events, imports, usage), and exposes it to AI coding agents via structured tools.
      7
      1
      MIT

    • sove-mcp

      JrKrishh
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude structural understanding of a codebase—dependency graph, entry points, complexity ranking, and import cycles—without reading every file into context.
      4
      MIT

    • solograph

      fortunto2
      A
      license
      A
      quality
      B
      maintenance
      Code intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.
      15
      4
      MIT

    • lovable-mcp-server

      hiromima
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for real-time analysis of Lovable-generated projects, enabling Claude Desktop to instantly understand project structure, components, dependencies, and more.
      39
      MIT

    • vue-ts-lsp

      enc0ded
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-contained MCP server providing type-aware code intelligence for TypeScript, JavaScript, and Vue files, exposing tools like hover, definition, references, and diagnostics to Claude Code without requiring global language server installations.
      MIT

    • ProPlan

      King-Proplan
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for project planning inside Claude. It tracks progress, knows your codebase, and resumes exactly where you left off every session.
      12 npm
      5
      -
    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.2/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of codebase analysis and testing, from finding dead code to auditing templates to verifying data flows. Even tools that seem similar (e.g., check_page vs. render_component vs. capture_flow) have clearly different scopes: one-time snapshot, component rendering, and multi-step flows, respectively. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., find_dead_code, get_component_detail, capture_flow). No mixing of conventions like camelCase or different verb styles. The naming is predictable and readable.

    Tool Count4/5

    21 tools is on the higher end but well-justified for a comprehensive codebase exploration and testing suite. Each tool serves a specific purpose, and the count reflects the breadth of features (catalog browsing, impact analysis, runtime verification, etc.) without feeling excessive.

    Completeness5/5

    The tool set covers the full lifecycle of codebase analysis: discovery (list/search), inspection (get_component_detail, get_data_flow), dependency mapping (get_dependency_chain, whats_affected), dead code detection, template auditing, runtime verification (check_page, render_component, capture_flow), and even login recovery. There are no obvious gaps for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources