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
      86 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.
      8
      17
      46,435
      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,022 PyPI
      1,447
      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
      398 npm
      82
      MIT

    TDQS

    A3.9/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target clearly distinct operations across indexing, graph, symbol, and context subdomains, and descriptions explicitly disambiguate near-pairs like codebase_index vs codebase_update and codebase_status vs codebase_graph_status. The main soft spots are codebase_symbol vs codebase_symbols (singular-plural distinction) and the three parallel '_remove' tools, which a hurried agent could misselect.

    Naming Consistency5/5

    Every tool uses a uniform snake_case 'codebase_<subdomain>_<action>' pattern with consistent subdomain prefixes (codebase_graph_*, codebase_context_*). The convention is predictable and readable throughout, with no mixing of styles.

    Tool Count3/5

    26 tools sits at the heavy end and only just clears the 25+ threshold, with notably deep sub-surfaces (7 graph tools, 4 context tools, 4 indexing tools). Each tool does something plausible, but the set is large enough that consolidation could reduce overhead.

    Completeness5/5

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

    Maintenance

    ActivityActive
    ResponsivenessResponsive