cocoindex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COCOINDEX_DB | Yes | Path to the local LMDB file for incremental state tracking (e.g., /path/to/.cocoindex/state.db). | |
| DATABASE_URL | Yes | PostgreSQL connection string (e.g., postgresql://user:password@host:port/database). It is highly encouraged to pass authentication through env vars. |
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 |
|---|---|
| index_repoB | Index a code repository (code-aware chunking, vendored dirs skipped). |
| index_documentsC | Index a document collection (markdown, text, PDF, ...). |
| searchA | Semantic search over indexed repos/documents. Optionally filter by source_kind ('repo' or 'document'). |
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 3 tools
Each tool has a clear and distinct purpose: indexing documents, indexing repos, and searching. There is no overlap or ambiguity.
Tool names follow a consistent snake_case pattern, with two using verb_noun (index_documents, index_repo) and one using a simple verb (search). This is mostly consistent with a minor deviation.
Three tools is a reasonable count for a focused indexing and search server. It covers the core functionality without being too sparse or excessive.
The tool surface covers the primary operations: indexing two types of content and searching across them. While there are no delete or update operations, the server appears to be scoped for basic indexing and retrieval, which is adequately covered.