document-index-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCUMENT_INDEX_OCR | No | OCR mode: auto or off. Default: auto. | auto |
| DOCUMENT_INDEX_OCR_LANG | No | OCR language. Default: eng. | eng |
| DOCUMENT_INDEX_MAX_FILE_MB | No | Maximum file size in MB. Files above this are refused. Raise it with --max-file-mb= or this environment variable. Default: 512. | 512 |
| DOCUMENT_INDEX_OCR_WORKERS | No | OCR workers. Default: 2. | 2 |
| DOCUMENT_INDEX_LIBRARY_PATH | Yes | Library root: one folder holding the documents you want indexed. It is a security boundary — the server refuses to read anything outside it, including through a symlink that lexically passes but physically escapes. | |
| DOCUMENT_INDEX_OCR_LANG_PATH | No | Path to tessdata_fast language files. Default: the CDN. |
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
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentA | Hybrid BM25 + semantic search across ingested documents. Returns ranked snippets with precise locators (page or section, section path, bbox). This is the usual starting point. It never returns full text — follow a hit with get_chunk_context using its chunk_id to read. |
| get_document_outlineA | Hierarchical heading tree with locators and chunk seq spans. Costs almost no context — use it to orient before targeted get_chunk_context reads, and jump straight to a section with document_id + chunk_seq_start. Never returns body text. Call it with no document_id to list the library. It also reports ingest progress: a document still being indexed shows status 'processing' with a rising chunk_count. |
| get_chunk_contextA | Full text of one chunk plus up to 5 neighbours on each side in reading order. Address it by chunk_id (from search results) OR by document_id + seq (from outline spans). This is the only tool that returns body text and it is hard-capped at ~24k characters — walk seq windows to read progressively. |
| ingest_documentA | Index a file from the library into the retrieval index. PDF, DOCX, Markdown and plain text are ingestible in this build; EPUB, PowerPoint, HTML and legacy binary Office (.doc) are recognised and refused with a reason naming the remedy. Scanned PDFs are detected and OCR'd automatically — expect those to index slowly, a few seconds per page. Format is decided by content rather than extension, which is why a mislabelled file is still routed correctly. Returns immediately with a document_id while indexing continues in the background — poll get_document_outline with that id to watch chunk_count rise and see when status becomes 'ready'. Re-ingesting an identical file is a no-op and returns the existing document_id. |
| delete_documentA | Remove a document from the index: its chunks, its full-text entries and its vectors. The source file on disk is never touched. Use it to drop something ingested by mistake — an edited file does NOT need this, because re-ingesting one already replaces the version it supersedes. Deletion is permanent; the document's chunk_ids stop resolving, and re-ingesting the file rebuilds it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ekelly95/document-index-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server