code-index-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| set_project_pathC | Set the base project path for indexing. |
| search_code_advancedA | Search for code pattern with pagination. Auto-selects best search tool (ugrep/ripgrep/ag/grep). Supports glob file_pattern (e.g., "*.py"), explicit regex mode, and fuzzy matching (ugrep only). Regex matching requires passing regex=True and may require an external search tool. |
| find_filesA | Find files matching glob pattern using in-memory index. Supports path patterns (.py, test_.js) and filename-only matching (README.md). |
| get_file_summaryB | |
| get_symbol_bodyA | |
| refresh_indexA | Manually rebuild the project file index. Use after git operations or when index seems stale. |
| build_deep_indexA | |
| get_settings_infoB | Get information about the project settings. |
| create_temp_directoryA | Create the temporary directory used for storing index data. |
| check_temp_directoryA | Check the temporary directory used for storing index data. |
| clear_settingsB | Clear all settings and cached data. |
| refresh_search_toolsA | Manually re-detect the available command-line search tools on the system. This is useful if you have installed a new tool (like ripgrep) after starting the server. |
| get_file_watcher_statusA | Get file watcher service status and statistics. |
| configure_file_watcherA | Configure file watcher service settings. |
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 14 tools
Each tool targets a distinct action: index building, file watching, settings management, searching, etc. Overlap is minimal and descriptions clarify the differences.
All tool names use a consistent verb_noun snake_case pattern (e.g., build_deep_index, check_temp_directory, get_file_summary). No mixing of conventions.
14 tools cover indexing, searching, file details, symbol retrieval, settings, and utilities. This is well-scoped for a code index server, neither sparse nor excessive.
Covers core operations: index build/refresh, file and code search, symbol body retrieval, settings, file watcher. Minor gaps like listing symbols or index statistics exist but do not hinder primary use.