SocratiCode Codebase Exploration

Use SocratiCode MCP tools to explore codebases efficiently. The core principle: search before reading — the index gives you a map of the codebase in milliseconds; raw file reading is expensive and context-consuming.

Workflow

1. Start most explorations with codebase_search

Hybrid semantic + keyword search (vector + BM25, RRF-fused) runs in a single call.

• Broad queries for orientation: "how is authentication handled", "database connection setup", "error handling patterns"
• Precise queries for symbol lookup: exact function names, constants, type names
• Prefer search results to infer which files to read — do not speculatively open files
• Use fileFilter to narrow to a specific file path, languageFilter for a specific language
• Adjust minScore (default 0.10) for precision vs recall — lower for more results, higher for stricter matching

When to use grep instead: If you already know the exact identifier, error string, or regex pattern, grep/ripgrep is faster and more precise — no semantic gap to bridge. Use codebase_search when exploring, asking conceptual questions, or when you don't know which files to look in.

2. Follow the graph before following imports

Use codebasegraphquery to see what a file imports and what depends on it before diving into its contents. This prevents unnecessary reading of transitive dependencies.

• codebasegraphquery — imports and dependents for any file (pass relative path)
• codebasegraphstats — architecture overview: total files, edges, most connected files, orphans, language breakdown
• codebasegraphcircular — find circular dependencies (these cause subtle runtime bugs; check proactively when debugging unexpected behaviour)
• codebasegraphvisualize — Mermaid diagram colour-coded by language, circular deps highlighted in red. Pass mode: "interactive" to open a self-contained HTML explorer (file + symbol views, blast-radius overlay, search, PNG export — works offline) instead.

The graph is auto-built after indexing. Use codebasegraphstatus to check if the graph is ready. In SOCRATICODEWATCHER=manual or off, graph queries do not create a missing graph; run codebasegraph_build explicitly when requested.

3. Read files only after narrowing via search

Once search results clearly point to 1-3 files, read only the relevant sections. Never read a file just to find out if it's relevant — search first.

A single codebase_search call returns ranked, deduplicated snippets from across the entire codebase in milliseconds. This gives you a broad map at negligible token cost — far cheaper than opening files speculatively.

4. Leverage context artifacts for non-code knowledge

Projects can define a .socraticodecontextartifacts.json config to expose database schemas, API specs, infrastructure configs, architecture docs, and other project knowledge that lives outside source code.

• codebase_context — list available artifacts (names, descriptions, paths, index status)
• codebasecontextsearch — semantic search across all artifacts (or filter with artifactName)
• Artifacts are auto-indexed on first search and auto-detect staleness

Run codebasecontext early to see what's available. Use codebasecontext_search before asking about database structure, API contracts, or infrastructure.

5. Check status if something seems wrong

• codebase_status — check index status, progress, watcher state, graph status
• If search returns no results, the project may not be indexed yet
• If the watcher is inactive, results may be stale — run codebase_update; start the watcher only when status does not say it is disabled
• In snapshot mode (SOCRATICODEWATCHER=off plus SOCRATICODEAUTO_RESUME=off), stale results are expected until an explicit update. Do not enable or start the watcher.

6. Get an overview of all tools

• codebase_about — quick reference of all SocratiCode tools and a typical workflow

Goal → Tool Quick Reference

For full parameter details on every tool, see [references/tool-reference.md](references/tool-reference.md).