AST-Navigator-MCP
Related Servers
Alternatives to AST-Navigator-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to get exact go-to-definition, find-references, hover, diagnostics, and file outline answers from existing language servers instead of grep. It is read-only and dependency-free.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to navigate and refactor a codebase through an AST index, offering project overviews, symbol and usage search, module dependency exploration, and LSP-backed operations such as rename, go-to-definition, diagnostics, and extract-method. Supports TypeScript/JavaScript and C# with automatic reindexing and watch mode.MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to perform zero-execution, AST-based static analysis of JavaScript/TypeScript codebases, including symbol lookup, dependency tracing, change-impact analysis, dead-code detection, and risk assessment.8750 npmMIT
- AlicenseBqualityBmaintenanceEnables coding agents to query a static AST-based call graph for TypeScript/JavaScript repositories, including who-calls, impact analysis, entry-to-dependency traces, hotspots, symbol search, and git-blame archaeology, with every result backed by source evidence chains.91MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to build a ranked, token-budgeted map of a codebase and query it for symbol definitions, callers, callees, and related files over stdio.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local MCP server that gives AI coding agents symbol definitions, dependency graphs, and a live architecture vocabulary for TypeScript/JavaScript repos, with no network or embeddings.16 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: single-file outline (get_file_structure), symbol definition search across a directory (find_definition), and per-file dependency listing (analyze_dependencies). Descriptions explicitly bound each other out (e.g. find_definition 'not for finding usages', analyze_dependencies 'not which files import it'), so an agent cannot easily misselect. Only minor overlap is that both get_file_structure and find_definition surface declarations, but their input shapes (filePath vs. name/directory) keep them separate.
All three names follow the same verb_noun snake_case convention (get_file_structure, find_definition, analyze_dependencies). Verb prefixes are meaningful and non-colliding, and no camelCase or V2-style variants appear.
Three tools is lean but appropriate for a narrow AST navigation server, and each earns its place without redundancy. It sits at the low edge of the ideal range, since the surface covers only the read/inspect direction of the domain.
Coverage of the stated read-only navigation domain is coherent — outline, definition lookup, and dependency graph — but there is no reference/usage search (explicitly disclaimed) and no reverse-dependency query, both core navigation operations. Agents must chain multiple find_definition calls, or cannot answer 'who uses this' at all.