anyindex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANYINDEX_DB | No | Path to the index database file. Defaults to <root>/.anyindex/index.db. | |
| ANYINDEX_ROOT | No | Absolute path to the project root to index. Defaults to the nearest repository root above the working directory, else the working directory. | |
| ANYINDEX_DTYPE | No | Model dtype. Defaults to q8. | |
| ANYINDEX_MODEL | No | Embedding model id. Defaults to jinaai/jina-embeddings-v2-base-code. | |
| ANYINDEX_WATCH | No | When true, watch the project and keep the index fresh. Defaults to false. | |
| ANYINDEX_MODELS | No | Path to the model cache directory. Defaults to the user cache directory plus anyindex-mcp/models. | |
| ANYINDEX_OFFLINE | No | When true, run offline using a warm model cache. Defaults to false. | |
| ANYINDEX_AUTOINDEX | No | When true, automatically build the index. Defaults to false. | |
| ANYINDEX_LOG_LEVEL | No | Log level for diagnostics written to stderr. Defaults to info. | |
| ANYINDEX_INDEX_ROOT | No | Path used for the index root. Defaults to the nearest repository root above --root, else --root. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_statusA | Reports whether the codebase index is ready to search, how many files and chunks it covers, and whether indexing is currently running. After calling index_update or index_rebuild, poll this to find out when the work finished. Also reports whether any subsystem failed, so you never rely on a silently broken index. |
| anyindex_searchA | Semantic and keyword search over the ENTIRE locally indexed codebase. Every indexed file is already available to you — do not ask the user to paste code, and do not read files directory-by-directory looking for it. Use this when the answer is not in your current context, when you need to locate a function, class or feature by name or by meaning, or when you need to understand how parts of the project fit together. Skip it when the answer is already in context, or for general programming questions unrelated to this repository. Each result carries file path and line numbers. If no results come back, the code may not exist here — say so instead of inventing it. |
| get_file_outlineA | Lists the symbols defined in one file — functions, classes, methods — with their line ranges and signatures. Cheaper than reading the file when you only need to know what it defines, or need to pick a line range to read. The index may be stale for very recent edits; verify with Read when exactness matters. |
| find_referencesA | Finds where an identifier is defined and where it is used, as file and line numbers. Use it before editing a shared function or type, to see what depends on it, or when you know the name but not the file. These are LEXICAL matches: a same-named identifier in another class, a comment or a string counts as a match too. It is not a call graph — it does not resolve which |
| index_updateA | Indexes files that changed since the last run and embeds the new chunks. Safe to call after edits; existing chunks are reused by content hash. Use it when the repository has been modified and the index is stale. |
| index_rebuildA | Discards the whole index and rebuilds it from scratch, including recomputing every embedding. Slow — minutes on a large repository. Use only when index_status reports an incompatibility, or after changing the embedding model. |
| pingA | Liveness probe. Returns the resolved configuration so client setup can be verified. |
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 7 tools
Tools cover distinct lifecycle stages (status, update, rebuild) and distinct retrieval modes (semantic search, symbol outline, lexical references). Minor overlap between anyindex_search and find_references when locating an identifier by name, but descriptions clarify the intended use cases.
Mixed conventions: index_* prefix for management tools is consistent, but anyindex_search has a redundant server prefix, and verbs like get_file_outline/find_references coexist with noun-like index_status and bare ping. Still readable but not uniform.
Seven tools are well-scoped for a codebase index/search server. Each tool has a clear role and no redundant or bloated surface.
Covers full index lifecycle (status, update, rebuild), search, file outline, references, and liveness. No obvious missing operation for the stated purpose.