doc-index
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@doc-indexsearch my documents for 'how to configure authentication'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Doc Index MCP
What is This For?
A local-first semantic search server for your documents. Index PDFs, Word docs, PowerPoints, Excel files, and text/markdown, then search them using natural language via the Model Context Protocol (MCP).
Semantic search - Find relevant content using natural language queries
Boundary-aware chunking - Respects document structure (chapters, sections, headers)
Table extraction - Extract tables from documents as CSV
Fully local - No external APIs, no cloud services, no Docker containers, no PyTorch
Lightweight - ONNX-based embeddings (~50MB vs ~2GB for PyTorch)
Related MCP server: ragi
Quick Start
1. Add to your MCP config
Requires uv. If you don't have uv, see Alternative Installation below.
Add to .mcp.json in your project root (for Claude Code) or your Claude Desktop config:
{
"mcpServers": {
"doc-index": {
"command": "uvx",
"args": ["doc-index-mcp"]
}
}
}2. Install the skill (optional)
The skill teaches the agent how to use the search tools effectively (token budgets, boundary expansion, structure-first retrieval):
uvx --from doc-index-mcp doc-index-install-skillThat's it — start asking Claude to index and search your documents.
Hermes Agent reads skills from ~/.hermes/skills/<category>/ rather than per-project, and configures MCP servers in ~/.hermes/config.yaml:
uvx --from doc-index-mcp doc-index-install-skill --target hermesmcp_servers:
doc-index:
command: uvx
args:
- doc-index-mcpThe installer honours HERMES_HOME, so non-default profiles install to the right place. Restart the Hermes session afterwards so the skill is picked up.
Supported Formats
Format | Extensions | Notes |
Text |
| Plain text |
Markdown |
| Preserves headers for boundaries |
| Text extraction with page markers | |
Word |
| Paragraphs, headings, tables |
PowerPoint |
| Slides, notes, tables |
Excel |
| Sheets as tables |
Why No External Services?
Component | Traditional RAG | This Server |
Embeddings | OpenAI API / hosted model | Local ONNX model (fastembed) |
Vector DB | Pinecone / Weaviate / Qdrant | Local file (usearch) |
Storage | Cloud / managed DB | Local |
Dependencies | PyTorch (~2GB) | ONNX Runtime (~50MB) |
Tools
doc_index
Index a document for semantic search.
{
"file_path": "docs/manual.pdf",
"source_name": "manual"
}doc_search
Search indexed documents using natural language.
{
"query": "how to configure authentication",
"top_k": 5,
"expand_to_boundary": "section",
"max_return_tokens": 4096
}Parameters:
query- Search querysources- Filter to specific sources (optional)top_k- Number of results (default: 5)expand_to_boundary- Expand results to full "chapter", "section", "subsection", or "page"max_return_tokens- Token budget for results (default: 4096)include_siblings- Include sibling sections when expanding
doc_list
List all indexed sources.
doc_chunk
Retrieve a specific chunk by ID with optional neighbors.
{
"chunk_id": "manual:42",
"neighbors": 2
}doc_toc
Get the table of contents (chapters, sections, subsections) for an indexed document. Use this to understand document structure before retrieving specific content.
{
"source_name": "manual",
"max_depth": 3
}doc_get_content
Retrieve document content by structural location. Provide exactly one locator: boundary_id, chapter, section, or pages.
{
"source_name": "manual",
"chapter": "3",
"max_return_tokens": 8192
}read_document
Read a document without indexing. Returns formatted text.
{
"file_path": "report.pdf",
"max_chars": 100000
}list_tables
List all tables in a document.
{
"file_path": "data.xlsx"
}extract_table
Extract a specific table as CSV.
{
"file_path": "data.xlsx",
"table_index": 0,
"max_rows": 100
}Environment Variables
Variable | Description | Default |
| Base directory for resolving file paths | Current working directory |
| Directory for storing vector indices |
|
Alternative Installation
Install globally with pip
pip install doc-index-mcpThen in your .mcp.json:
{
"mcpServers": {
"doc-index": {
"command": "doc-index-mcp"
}
}
}Install from source
Clone the repo and install dependencies:
git clone https://github.com/mike-anderson/doc-index-mcp.git
cd doc-index-mcp
pip install -e .Then point your .mcp.json at the server entrypoint:
{
"mcpServers": {
"doc-index": {
"command": "python",
"args": ["/path/to/doc-index-mcp/src/server.py"]
}
}
}Architecture
Everything runs locally - no external APIs, databases, or embedding servers required.
flowchart TB
subgraph Client["MCP Client (Claude Desktop, etc.)"]
LLM[LLM]
end
subgraph MCP["Doc Index MCP Server"]
Server[server.py]
subgraph Services["Local Services"]
Loader[Document Loader<br/>PDF, DOCX, PPTX, XLSX]
Chunker[Boundary-Aware<br/>Chunker]
Embedder[Embedder<br/>ONNX Runtime]
VectorStore[Vector Store<br/>usearch]
end
end
subgraph Storage["Local Filesystem"]
Docs[(Source<br/>Documents)]
Index[(".docindex/<br/>├── manifest.json<br/>└── vectors/<br/> ├── index.usearch<br/> ├── chunks.jsonl<br/> └── boundaries.json")]
end
subgraph Models["Embedded Model (downloaded once)"]
ONNX[BAAI/bge-small-en-v1.5<br/>ONNX format ~50MB]
end
LLM <-->|MCP Protocol| Server
Server --> Loader
Server --> Chunker
Server --> Embedder
Server --> VectorStore
Loader -->|read| Docs
VectorStore <-->|read/write| Index
Embedder -->|load once| ONNX
style Client fill:#e1f5fe
style Storage fill:#fff3e0
style Models fill:#f3e5f5
style MCP fill:#e8f5e9Data Flow
flowchart LR
subgraph Index["Indexing"]
direction TB
A[Document] --> B[Load & Extract Text]
B --> C[Detect Boundaries]
C --> D[Chunk ~256 tokens]
D --> E[Generate Embeddings]
E --> F[Save to Disk]
end
subgraph Search["Searching"]
direction TB
G[Query] --> H[Embed Query]
H --> I[Vector Similarity Search]
I --> J[Expand to Boundaries]
J --> K[Return Results]
end
Index -.->|stored in .docindex/| SearchLicense
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
The Needle MCP server enables semantic search on documents stored in files like PDFs, DOCX, and XLSX by connecting AI applications to external data sources. It provides capabilities to create and manage document collections, perform natural language searches on stored content, and retrieve relevant information without requiring exact keyword matches.
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Personal knowledge base MCP server with semantic search, auto-categorization, metadata extraction
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server that enables semantic search and retrieval of documentation using a vector database (Qdrant). This server allows you to add documentation from URLs or local files and then search through them using natural language queries.33 npm136Apache 2.0
- AlicenseAqualityDmaintenanceLocal-first RAG indexing and semantic search MCP server. Enables document retrieval and context-aware queries using local embedding models.36 npmMIT
- AlicenseAqualityDmaintenanceA local-first document retrieval MCP server that enables AI coding tools like Codex to search private local documents via semantic search and keyword boost, supporting ingestion of PDF, DOCX, TXT, Markdown, and HTML files.7MIT
- AlicenseAqualityBmaintenanceA local-first MCP server that ingests PDFs, extracts structure, and provides semantic search and sequential navigation tools for AI clients to query and learn from documents.10MIT