codetree
Related Servers
Alternatives to codetree
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query a pre-built semantic knowledge graph of code, reducing token usage and tool calls. Supports 16 tools for code exploration, analysis, and context building.5 npm7MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query code structure efficiently through 16 MCP tools, including symbol lookup, full-text search, dependency analysis, and refactor planning, powered by tree-sitter parsing and index-backed code intelligence.3MIT
- AlicenseNot gradedqualityCmaintenanceProvides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.9 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables precise code extraction from 30+ languages using tree-sitter parsing, allowing AI assistants to retrieve functions, classes, and code snippets with accurate line numbers.8MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.8-
- AlicenseAqualityDmaintenanceEnables AI assistants to understand and navigate codebases through structural analysis. Provides code mapping, symbol search, and impact analysis using ast-grep for accurate parsing of Python, JavaScript, TypeScript, and Go projects.452MIT
TDQS
Scored across 23 tools
Each tool has a clearly distinct purpose, with no overlapping or ambiguous functionality. Tools like `get_symbol` and `get_symbols` are differentiated by scope, and `search_graph` vs `search_symbols` target different aspects of the codebase.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., `analyze_dataflow`, `find_references`, `get_call_graph`). Naming conventions are uniform, making the tool set predictable and easy to navigate.
With 23 tools, the set is slightly larger than typical but remains well-scoped for a comprehensive code analysis server. Each tool serves a distinct purpose, and the count feels justified by the breadth of analysis features offered.
The tool set covers the full spectrum of static code analysis: exploration (repository map, skeletons), dependency analysis (call graph, dependency graph), quality checks (complexity, clones, dead code), and context (git history, test finding). No obvious gaps for the stated purpose.