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.1686 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.81746,435MIT
- 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,022 PyPI1,447MIT
- 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.36398 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
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.
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.
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.
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.