ContextTree MCP
Related Servers
Alternatives to ContextTree MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to perform intelligent semantic code search across codebases using local AI embeddings for meaning-based retrieval.634 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to perform semantic code search locally, finding code by meaning rather than exact keywords.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to search codebases by meaning using local AI embeddings, with tools for indexing, cache management, workspace switching, status checks, and package version lookup. It supports incremental and progressive indexing with configurable embedding dimensions to find relevant code even when terminology differs.34 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search for AI assistants by indexing codebases with embeddings and Tree-sitter, returning relevant snippets via natural language queries.15MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to search codebases by meaning using local AI embeddings, with tools for indexing, cache and workspace management, status checks, and latest package-version lookup.34 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to search codebases by meaning using local AI embeddings, so they can find relevant code even when terminology differs, while also offering package version lookup, indexing, cache, workspace, and status tools.34 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct part of code navigation: semantic search vs. exact definitions vs. AST usages vs. index maintenance. There is no realistic confusion between their purposes.
Three of four tools use imperative verb-first names (find_ast_usages, index_workspace, go_to_definition), and all are snake_case. semantic_search breaks the pattern slightly by starting with an adjective instead of a verb, but the naming remains readable and predictable.
With 4 tools, the server is well-scoped and each tool earns its place in the code indexing/search/navigation workflow. There is no redundancy or bloat.
The core lifecycle is covered: index the workspace, search semantically, go to definitions, and find AST usages. Minor gaps such as no explicit index status or reset operation prevent a perfect score, but agents can work around them.