Skip to main content
Glama
aimasteracc

tree-sitter-analyzer

by aimasteracc

Related Servers

Alternatives to tree-sitter-analyzer

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Token-efficient code intelligence MCP server that indexes codebases with tree-sitter AST parsing and provides 150 tools for AI agents, using 61-95% fewer tokens than traditional grep/Read workflows.
      693 npm
      4
      Business Source 1.1
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local-first code intelligence, providing structural code graph, semantic search, and impact analysis to AI agents.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that builds a local code intelligence layer, letting AI agents explore call graphs, blast radius, and source slices via a single tool without external APIs.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local repository intelligence MCP server that builds a reusable graph of code structure for AI coding agents, providing 34 network-free tools for understanding, searching, and analyzing repositories without data leaving the machine.
      76 npm
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Ultra-lightweight, local-first MCP server for AI-powered code intelligence, providing AST-based analysis and 20+ tools while ensuring zero data leakage.
      85 npm
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Give your AI coding agents superpowers — a local MCP server for fast, token-efficient code navigation, search & analysis.
      -

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation2/5

    Eight facade tools bundle many actions, and their boundaries are porous: search and nav both advertise multi-hop/impact/UQL, nav and edit both expose impact, viz and index both expose knowledge, and health/project both expose overview. An agent can often justify several entry points for the same question, so misselection is likely despite detailed action lists.

    Naming Consistency3/5

    Most tools are single-word noun facades (viz, search, nav, edit, health, index, project, structure), but set_project_path is a verb_noun setup tool and abbreviations like viz/nav break the pattern. The convention is mixed but still readable.

    Tool Count4/5

    Nine top-level tools is a sensible count and the facade grouping keeps the surface navigable. However, each facade hides 8-16 actions, so the effective operation count is much larger than nine and some facades are overstuffed.

    Completeness4/5

    The surface covers index lifecycle, search/navigation, structural analysis, health, edit/refactor, visualization, and project intelligence, which is broad coverage for a code-intelligence server. No obvious lifecycle dead end exists, though some operations such as test execution or documentation generation are only implied or partial.

    Maintenance

    ActivityActive
    ResponsivenessResponsive