codebase-memory-mcp vs SocratiCode
Local MCP codebase search and analysis tools compared
codebase-memory-mcp and SocratiCode both provide local-first codebase context to MCP-compatible coding agents, combining search with code-relationship analysis. codebase-memory-mcp centers on a persistent structural knowledge graph, while SocratiCode combines semantic and keyword search with dependency graphs and searchable project artifacts.
codebase-memory-mcp: Build a Searchable Code Knowledge Graph
A local MCP server that indexes repositories into a persistent graph of code structure and relationships. It helps AI coding agents answer architectural and code-navigation questions with focused queries instead of repeated file searches.
SocratiCode: Give AI Agents Searchable Codebase Context
SocratiCode is a local-first MCP server and plugin that helps AI agents explore large codebases with semantic search, dependency graphs, and symbol-level impact analysis. It also indexes project context such as API specs and database schemas.
| codebase-memory-mcp | SocratiCode | |
|---|---|---|
| Language | C | TypeScript |
| License | MIT | AGPL-3.0 |
| Stars | 45.7k | 3.3k |
| Forks | 3.8k | 430 |
| Last analyzed | Oct 3, 2026 | Oct 12, 2026 |
Key differences
- codebase-memory-mcp stores code relationships in a local SQLite graph; SocratiCode fuses semantic and BM25 keyword search through Qdrant alongside its code graphs.
- codebase-memory-mcp can link HTTP routes and calls across services and index Dockerfiles and Kubernetes resources; SocratiCode can index API specifications, database schemas, and infrastructure configuration.
- codebase-memory-mcp is written in C and licensed under MIT; SocratiCode is written in TypeScript and licensed under AGPL-3.0.
- SocratiCode's default local setup relies on Docker for Qdrant and usually Ollama, with external embedding providers and Qdrant also configurable; codebase-memory-mcp stores its graph locally in SQLite.
- SocratiCode supports cross-project search, branch-aware indexing, and shared indexes for multiple agents; codebase-memory-mcp supports one-shot CLI access and multiple coding-agent clients.
Choose codebase-memory-mcp if you…
- need a persistent SQLite graph for structural queries and code-relationship analysis.
- want to trace routes and calls across services or index Dockerfiles and Kubernetes resources.
- prefer an MIT-licensed project written in C.
Choose SocratiCode if you…
- want semantic and keyword search alongside dependency graphs and symbol-level impact analysis.
- need to search API specifications, database schemas, or infrastructure configuration with source code.
- want cross-project search, branch-aware indexing, or shared indexes for multiple agents.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.