Skip to main content
Glama

Related Servers

Alternatives to SocratiCode

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      A fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.
      16
      51 npm
      13
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 159 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.
      2
      17
      48,005
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local-first codebase intelligence tool that enables AI assistants to research codebases using semantic search, multi-hop relationship discovery, and structural parsing. It allows users to extract architectural patterns and institutional knowledge across 30+ programming languages through an MCP-compatible interface.
      2
      1,717 PyPI
      1,455
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turn your codebase into AI context — entirely on your machine. Single-binary MCP server with AST parsing, call graph, and local embeddings.
      26
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first code intelligence MCP server with hybrid BM25 + ONNX vector search, symbol-level impact analysis, diff-aware PR review with risk scoring, and persistent memory tied to git state.
      36
      337 npm
      82
      MIT

    TDQS

    A3.8/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools map to distinct subsystems (indexing, graph, symbols, context, search) with detailed descriptions that clarify boundaries. A few pairs could still be momentarily confused — codebase_status vs codebase_graph_status, and codebase_context_index vs codebase_context_search (which auto-indexes) — but the descriptions explicitly disambiguate them.

    Naming Consistency5/5

    Every tool is snake_case with a consistent codebase_ prefix and predictable sub-namespaces (codebase_graph_*, codebase_context_*). Verb/noun structure is stable across list/build/query/status/remove operations.

    Tool Count3/5

    26 tools is on the heavy side and sits above the ideal band, but the breadth is explained by four genuine subsystems (index lifecycle, dependency graph, symbol intelligence, context artifacts). Some redundancy (multiple status and remove tools) keeps it from feeling tightly scoped.

    Completeness5/5

    The surface covers the full lifecycle: index/update/stop/remove/prune/watch/status/list for indexing, build/query/stats/circular/visualize/remove for the graph, and list/search/index/remove for context, plus symbol detail, impact and flow analysis. No obvious dead ends for the stated code-intelligence purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive