Skip to main content
Glama
Treeweft

treeweft-mcp

Official
by Treeweft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to treeweft-mcp

No user-submitted related servers found.

    Related Servers

    • semhood

      AhmeedGamil
      A
      license
      Not graded
      quality
      C
      maintenance
      AST-aware semantic code search engine for AI agents, enabling code retrieval by intent with call-graph context and optional LLM enrichment.
      1
      MIT

    • MindGraph

      dycm8009
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.
      31 npm
      MIT
    • oxcode by oxgraph

      oxcodeofficial

      oxgraph
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to navigate and query source code by providing context, symbols, and call graph information through a graph index.
      4
      MIT

    • droste-memory

      lorismascio17
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with causal code memory by indexing repositories into a graph of symbols and edges, enabling context-aware retrieval of relevant code slices.
      23 PyPI
      3
      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.8/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: indexing scopes, job tracking, search, and graph traversal are easy to separate. The main ambiguity is between search_code, search_code_enhanced, and explain_code, and between find_callers and find_references, but the descriptions give enough usage guidance to make the intended choice.

    Naming Consistency4/5

    The set mostly follows a clean verb_noun snake_case pattern: index_*, get_*, list_*, find_*. Minor deviations like 'source_staleness' (a noun phrase instead of a verb), 'search_code_enhanced' (suffix modifier), and 'rebuild_all_graphs' (bulkier form) keep it from a perfect 5.

    Tool Count3/5

    20 tools is on the heavy side, and several are near-variants of the same operation: three search entry points and two graph-build tools add surface area. However, the server covers distinct responsibilities—indexing, job management, search, and graph analysis—so the count is not unreasonable.

    Completeness4/5

    The surface covers the full indexing lifecycle—create, list, track, force-reindex, and remove—along with code search and graph navigation. Minor gaps remain, such as no dedicated source-detail tool, no scoping for find_callers, and no explicit incremental update beyond force reindexing.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources