Socraticode MCP Server

Repository exploration in SocratiCode begins with background indexing that saves progress for later resumption. After indexing finishes, assistants can retrieve code passages with natural-language queries using combined semantic and BM25 search. A file watcher refreshes the index after edits and catches changes made between sessions; an explicit update tool reindexes only changed files. Status checks report indexing progress and watcher state, while separate tools list indexed projects or remove their indexes. The default deployment runs locally through Docker, with cloud options available for embeddings and Qdrant.

For change analysis, dependency tools map import relationships, identify cycles, and show which files rely on a target. Symbol tools expose definitions, callers, and callees; execution tracing follows calls from an entry point, and impact analysis reports potentially affected files or functions. Graphs can be presented as Mermaid diagrams or explored in an offline browser view. Separate context tools discover and search configured database schemas, API specifications, infrastructure configurations, and architecture documents. Context search indexes artifacts on first use and detects stale content. Health checks cover Docker, Qdrant, Ollama, and the embedding model.