SocratiCode MCP
A local codebase index for agents: hybrid search, dependency graphs and change impact analysis
- 3,358 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- Reads the whole project codebase and starts Docker containers
Install
- Works in
Manual install
{
"mcpServers": {
"socraticode": {
"command": "npx",
"args": ["-y", "--prefer-online", "socraticode@latest"]
}
}
}Docker must be running
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads the whole project codebase and starts Docker containers
This is third-party code. Review the repository files before installing.
What it does
SocratiCode indexes a repository and gives the agent MCP tools for code search that fuse semantic search with BM25. It builds dependency graphs across many languages, finds circular imports and shows which symbols a change will affect. Database schemas, API specs and infra configs can be indexed too. By default Qdrant and Ollama run in Docker on your machine, the index updates as files change and several agents can share it.
Who it is for. For developers using agents on large repositories who do not want code to leave their machine.
Good fit when
- The agent burns tokens on grep and file reads in a large repository
- You need to know what breaks if a function or module changes
- You need an architecture map and circular dependency report
Not a fit when
- The project is small and plain search is enough
- Docker cannot run on the machine
Example request
Index the repository and show which modules depend on the auth serviceMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Requires Node.js 18.17 or newer and a running Docker for local Qdrant and Ollama. Indexing a large repository first takes time and resources. Cloud embeddings from OpenAI or Gemini are optional and need keys. Licensed AGPL-3.0; a hosted version is in private beta.
How to disable. Remove the socraticode block from the MCP config or uninstall the Claude Code plugin, then stop the project's Docker containers.
FAQ
Does code go to the cloud?
Not by default: embeddings and the vector store run locally in Docker and no API keys are needed.
How does the plugin differ from the MCP server?
The Claude Code, Codex and Cursor plugins add skills with instructions; a direct MCP install ships only the engine.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that indexes code with tree-sitter and returns individual functions and classes to the agent instead of whole files
An MCP server that builds a code graph of functions, classes, calls and routes and answers the agent's structural queries locally
Local code graph for agents: an MCP server returns entry points, symbol links and change impact in one call
A local MCP server and CLI for agents: semantic code search, call graphs and change-impact analysis
A structural code search MCP server for agents: finds the right file by query intent and runs locally
An MCP server that indexes a local repository with tree-sitter and gives the agent code search, file lookup and a structure summary of a file
README in short
The README presents SocratiCode as a codebase context engine and cites its own benchmark on the VS Code repository against grep-based exploration. It installs as a Claude Code, Codex or Cursor plugin, a VS Code extension, or an npx MCP server in any client. Environment variables, ignore rules, context artifacts, Docker resources and updates are covered in detail. The repo ships codebase-exploration and codebase-management skills.