Skip to main content
Glama
chelslava

ContextTree MCP

by chelslava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ContextTree MCP

No user-submitted related servers found.

    Related Servers

    • smart-coding-mcp

      amalikn
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform intelligent semantic code search across codebases using local AI embeddings for meaning-based retrieval.
      6
      12 npm
      MIT

    • CodeGrok MCP

      dondetir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic code search for AI assistants by indexing codebases with embeddings and Tree-sitter, returning relevant snippets via natural language queries.
      15
      MIT

    • code-search-mcp

      genautkin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to semantically search codebases by meaning rather than exact text, with zero external daemons and fully local embeddings. Works out-of-the-box with Claude Code, Gemini CLI, Antigravity, and Cursor.
      4
      MIT

    • Paparats MCP

      IBazylchuk
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.
      11
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources