code-index-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QDRANT_URL | No | Qdrant endpoint | http://localhost:6333 |
| QDRANT_API_KEY | No | Optional Qdrant key | |
| CODE_INDEX_ROOT | No | Default project root (single-project / fallback) | . |
| CODE_INDEX_SEMANTIC | No | Set 0 to disable semantic layer | 1 |
| CODE_INDEX_CACHE_HOME | No | Where SQLite indexes live | ~/.cache/code-index |
| CODE_INDEX_CONFIG_HOME | No | Where projects.toml lives | ~/.config/code-index |
| CODE_INDEX_EMBED_MODEL | No | fastembed model | BAAI/bge-small-en-v1.5 |
| CODE_INDEX_REINDEX_ON_START | No | 1 = background reindex on server start | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_textA | Exact full-text search across a service (FTS5). Returns path:line: content. Use for known strings, identifiers, config keys, error messages. Supports
FTS5 syntax, e.g. "foo AND bar", "exact phrase", prefix*.
|
| search_symbolB | Find symbol definitions (function/class/method/record/...) by name. Use to jump to where something is DEFINED. Set exact=true for an exact name
match, otherwise substring matching is used. |
| file_symbolsA | List all symbols (outline) of a single file, ordered by line. |
| search_semanticA | Fuzzy meaning-based search (vector similarity via Qdrant). Use for conceptual queries like "where do we validate refunds" when you
don't know exact identifiers. |
| search_hybridA | Best-effort combined search: symbols + text + semantic for one service. Prefer this when you're not sure which layer fits. |
| list_servicesA | List indexable microservices from the external registry. Returns name, id and path for each. Pass a name or id as the |
| reindexA | Rebuild the index from disk for one service. Use after large changes. full=true forces a complete re-index; otherwise only changed files are updated. |
| index_statsB | Show how many files and symbols are currently indexed for a service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct purpose: file_symbols for file outline, index_stats for statistics, list_services for service listing, reindex for rebuilding, and four differentiated search tools (hybrid, semantic, symbol, text) with clear guidance on when to use each.
All tool names follow a consistent snake_case verb_noun pattern (e.g., search_hybrid, file_symbols, list_services), making the set predictable and easy to navigate.
With 8 tools, the surface is well-scoped for a code index server: listing, stats, rebuilding, and four search variants cover the core functionality without bloat.
The tool set covers essential operations (list services, rebuild index, search, show file symbols) but lacks granular index management (e.g., individual file add/remove) and cross-service search, limiting flexibility in some workflows.