SocratiCode
Related Servers
Alternatives to SocratiCode
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA 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.1651 npm13MIT
- AlicenseBqualityAmaintenanceHigh-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.21748,005MIT
- AlicenseAqualityAmaintenanceA 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.21,717 PyPI1,455MIT
- AlicenseNot gradedqualityCmaintenanceTurn your codebase into AI context — entirely on your machine. Single-binary MCP server with AST parsing, call graph, and local embeddings.26MIT
- AlicenseAqualityAmaintenanceLocal-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.36337 npm82MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
TDQS
Scored across 26 tools
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.
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.
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.
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.