tree-sitter-analyzer
Related Servers
Alternatives to tree-sitter-analyzer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceToken-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.163 npm4Business Source 1.1
- AlicenseNot gradedqualityAmaintenanceMCP server for local-first code intelligence, providing structural code graph, semantic search, and impact analysis to AI agents.2MIT
- AlicenseNot gradedqualityAmaintenanceMCP 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
- AlicenseNot gradedqualityAmaintenanceLocal 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.40 npmMIT
- AlicenseNot gradedqualityAmaintenanceUltra-lightweight, local-first MCP server for AI-powered code intelligence, providing AST-based analysis and 20+ tools while ensuring zero data leakage.869 npm10MIT
- FlicenseNot gradedqualityDmaintenanceGive your AI coding agents superpowers — a local MCP server for fast, token-efficient code navigation, search & analysis.-
TDQS
Scored across 9 tools
Several facades overlap heavily: project and health both offer overview/project/file metrics, nav/search/structure all handle symbol lookup and traversal, and edit/nav both include impact analysis. The action descriptions are detailed, but an agent still has multiple plausible entry points for common tasks like 'find a symbol' or 'check project health'.
Most tools are single-noun facades (project, search, nav, structure, health, edit, index, viz), but set_project_path follows a verb_noun pattern and abbreviations like nav/viz break the otherwise noun-based convention. The names remain readable, but the convention is mixed.
Nine top-level tools is within the reasonable range, and each facade represents a real domain area. However, each tool bundles many actions, making the effective surface much larger and heavier than the count suggests.
The surface covers project setup, indexing lifecycle, search, navigation, structural analysis, health metrics, edit safety, and visualization. For a code-intelligence analyzer, this is comprehensive with no obvious major gaps.