ast-mcp
Related Servers
Alternatives to ast-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables LLM agents to navigate source code structurally via tree-sitter over MCP, offering outline-based reading, AST pattern search, workspace-scale symbol indexing, call graph analysis, and built-in security audit queries.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to query a codebase's structural knowledge (symbols, imports, call graphs, etc.) via MCP, reducing tokens and improving correctness compared to raw file access.35 npm7MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to efficiently explore codebases by providing structural outlines, module digests, symbol bodies, and AST-aware grep via MCP.44 npm1MIT
- AlicenseNot gradedqualityAmaintenanceStandalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceA lightweight, zero-configuration MCP server for source code analysis with GraphRAG capabilities, enabling structural understanding and efficient code completion from MCP-compatible AI tools.48 PyPI13MIT
TDQS
Scored across 6 tools
Most tools target clearly distinct operations: repository search, single-file outline, raw AST query, imports/exports, and symbol lookup. The main ambiguity is between get_docstrings and get_symbol with mode 'doc', which could serve similar documentation-retrieval purposes.
All names are readable snake_case, but the pattern is mixed: get_docstrings and get_symbol use 'get_', while file_outline, ast_query, list_imports, and search_symbols each start with a different noun or verb. There is no single consistent verb_noun convention, though the names are still predictable enough to navigate.
Six tools is a well-scoped size for an AST/source-analysis server. Each tool covers a meaningful slice of the domain without redundancy or bloat, and ast_query exists as an intentional escape hatch rather than a loosely-scoped extra.
The set covers documentation extraction, file outlining, symbol lookup and search, imports/exports, and raw AST querying, which forms a coherent lifecycle for source exploration. The ast_query escape hatch explicitly fills any gap left by the typed tools, so agents can handle cases outside the common patterns.