LocalDocs MCP
Creates a local database of indexed technical documentation from web crawls and local files, enabling AI agents to efficiently search and retrieve documentation through MCP tools.
README
LocalDocs MCP
A Model Context Protocol (MCP) server that creates a local database of indexed and optimized technical documentation. It enables AI agents to efficiently query, search, and retrieve documentation from both web sources and local files through MCP tools.
Features
- Web Crawling: Automatically crawl and index documentation websites
- Local File Indexing: Process local markdown documentation
- AI-Powered Processing: Optional AI enhancement for metadata extraction and example generation
- Smart Search: Fuzzy search and semantic retrieval capabilities
- Efficient Storage: Folder-based markdown storage with frontmatter metadata
- MCP Integration: Full MCP protocol support for AI agent interaction
- Async Architecture: Fast, concurrent processing throughout
Installation
# Install from source
git clone https://github.com/dylan-gluck/localdocs-mcp
cd localdocs-mcp
uv sync
# Run directly with uvx (coming soon)
# uvx localdocs-mcp
Quick Start
1. Initialize a Documentation Collection
# Crawl web documentation
localdocs init react --crawl https://react.dev/learn --depth 2
# Index local files
localdocs init myproject --local ~/Documents/myproject/docs
# With AI processing (requires OpenAI API key)
localdocs init vue --crawl https://vuejs.org/guide/ --ai
2. Search Documentation
# Search across all collections
localdocs search "useState hook"
# Search specific collection
localdocs search "component props" --collection react
# List all collections
localdocs list
3. Configure MCP Client
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"localdocs": {
"command": "uvx",
"args": ["localdocs-mcp", "serve"],
"env": {
"OPENAI_API_KEY": "${OPENAI_API_KEY}" // Optional, for AI processing
}
}
}
}
MCP Tools
The server exposes the following tools to AI agents:
| Tool | Description | Parameters |
|---|---|---|
search_docs |
Search across all documentation | query, collection?, limit? |
list_collections |
List available collections | - |
get_document |
Get specific document by ID | doc_id |
list_examples |
List code examples | collection?, language? |
fuzzy_find |
Fuzzy search documents | pattern, collection? |
CLI Commands
Collection Management
# Initialize new collection
localdocs init <name> --crawl <url> [--depth N] [--ai]
localdocs init <name> --local <path> [--ai]
# List collections
localdocs list
# Update existing collection
localdocs update <name>
# Delete collection
localdocs delete <name>
Document Operations
# Search documents
localdocs search <query> [--collection NAME] [--limit N]
# Show specific document
localdocs show <doc-id>
# Get statistics
localdocs stats [--collection NAME]
MCP Server
# Start MCP server (stdio transport)
localdocs serve
# Start with HTTP transport (coming soon)
localdocs serve --port 8080
Configuration
LocalDocs stores configuration in ~/.localdocs-mcp/config.yaml:
storage_path: ~/.localdocs-mcp
default_collection: main
crawl_defaults:
depth: 2
word_count_threshold: 50
excluded_tags: [nav, footer, header]
cache_enabled: true
processing:
chunk_size: 2000
overlap: 200
generate_examples: true
baml:
model: gpt-4o-mini
temperature: 0.3
Development
# Install dependencies
uv sync
# Run tests
uv run pytest tests/
# Run specific test file
uv run pytest tests/test_storage.py -v
# Lint and format code
uvx ruff check .
uvx ruff format .
# Type checking
uv run mypy localdocs
Architecture
LocalDocs follows a modular architecture:
- CLI Layer: Typer-based command interface
- Processing Layer: Web crawling (Crawl4ai) and document processing
- Storage Layer: File-based storage with markdown and frontmatter
- MCP Layer: FastMCP server implementation
- AI Layer: Optional BAML integration for enhanced processing
Storage Format
Documents are stored as markdown files with YAML frontmatter:
---
id: "uuid-here"
collection: "react"
source_url: "https://react.dev/learn/thinking-in-react"
title: "Thinking in React"
chunk: 1
total_chunks: 3
tags: ["react", "component", "state"]
created: 2025-09-04
examples_generated: true
---
# Thinking in React (Part 1/3)
[Document content here]
## Generated Examples
[Example code blocks]
Environment Variables
OPENAI_API_KEY: Required for AI-powered processing featuresANTHROPIC_API_KEY: Alternative AI provider for processingLOCALDOCS_PATH: Override default storage path
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License - see LICENSE file for details
Roadmap
- [ ] Vector embeddings for semantic search
- [ ] Support for more file types (PDF, docx)
- [ ] HTTP transport option for MCP
- [ ] Incremental indexing
- [ ] Web UI for document browsing
- [ ] Custom BAML prompts
- [ ] Multi-language code detection improvements
Acknowledgments
Built with:
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。