Skip to main content
Glama
jamcgrath

svelte-component-graph-mcp

by jamcgrath

Related Servers

Alternatives to svelte-component-graph-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps the Svelte Language Server to provide IDE-like tools for Claude Code and other MCP clients. It enables advanced Svelte development features including symbol navigation, diagnostics, refactoring, and component-specific analysis.
      21
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that indexes your codebase using tree-sitter AST parsing and gives AI tools instant access to structural intelligence like dependency graphs, call trees, and dead code detection from a local SQLite database.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, zero-configuration MCP server for source code analysis with GraphRAG capabilities, enabling structural understanding and efficient code completion from MCP-compatible AI tools.
      12
      MIT
    • 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

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the component graph: global view (get_graph), per-node detail (get_component), unused analysis (get_unused), route view (get_routes), and cache refresh (scan). There is no functional overlap.

    Naming Consistency4/5

    Four tools consistently follow the 'get_' prefix pattern, while 'scan' is a bare verb, which is a minor deviation but still understandable.

    Tool Count5/5

    With five tools, the server strikes a good balance—neither too sparse nor overwhelming for its focus on graph analysis.

    Completeness5/5

    The tools cover all necessary operations for a read-only component graph server: fetching the full graph, drilling into a component, finding unused components, routing information, and cache invalidation. No obvious missing capability.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues