mcp-documentation-server

Indexes documents into a local vector database for hybrid semantic search via MCP.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/mcp-skills --skill mcp-documentation-server-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-documentation-server
Source: https://github.com/reason-machines/mcp-skills/tree/main/skills/mcp-documentation-server
Command: npx skills add https://github.com/reason-machines/mcp-skills --skill mcp-documentation-server-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and individuals accumulate scattered documentation that is hard to search meaningfully; keyword search misses context and cloud-based search raises privacy concerns. This Skill runs a local-first MCP server that ingests documents, chunks them intelligently, and makes them searchable by meaning. ## Core Features & Use Cases - Hybrid Semantic Search: Combines full-text and vector search across all documents using an embedded Orama database with parent-child chunking for richer context. - Document Management: Add, list, retrieve, and delete documents, or drop .txt, .md, and .pdf files into an uploads folder for batch processing. - Optional Gemini AI Search: Ask natural-language questions across selected documents with conversation history when a GEMINI_API_KEY is configured. - Use Case: A developer drops API guides and runbooks into the uploads folder, runs process_uploads, then queries "rate limiting configuration" from their MCP client and retrieves the exact section plus surrounding context. ## Quick Start Add the documentation server to my MCP client configuration using npx @andrea9293/mcp-documentation-server and index my markdown files for semantic search.

Frequently Asked Questions about mcp-documentation-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add semantic search to my local documents?▼

Run the MCP documentation server via npx and add documents with the add_document tool or drop .txt, .md, and .pdf files into the uploads folder and call process_uploads. Then use search_all_documents for hybrid full-text and vector search across everything indexed.

What embedding models does the MCP documentation server support?▼

It supports Xenova/all-MiniLM-L6-v2 (384 dimensions, ~80MB) as the fast default and Xenova/paraphrase-multilingual-mpnet-base-v2 (768 dimensions, ~420MB) for higher quality multilingual search. Changing models requires re-indexing all documents because embeddings are incompatible.

Does the documentation server work without a Gemini API key?▼

Yes, all core features including document management, file processing, and hybrid semantic search work fully offline with local embeddings. The GEMINI_API_KEY is only required for the optional search_documents_with_ai tool that generates conversational answers.

Why does semantic search return no results after setup?▼

Missing results usually mean the embedding model failed to download. Check ~/.cache/huggingface/ for the model files, clear the cache to force a re-download, and restart the server so embeddings generate correctly.

How do I handle large files that fail to process?▼

Enable streaming mode with MCP_STREAMING_ENABLED=true and lower MCP_STREAM_FILE_SIZE_LIMIT, for example to 5MB, so large files are read in 64KB chunks instead of loading entirely into memory. This prevents timeouts and out-of-memory crashes.