DocNav-MCP
Enables loading and working with documents from GitHub repositories, supporting document analysis and navigation through GitHub-hosted content.
Provides document navigation, content extraction, and search capabilities for Markdown files, allowing analysis and intelligent interaction with Markdown document structure and content.
DocNav MCP Server
DocNav is a Model Context Protocol (MCP) server which empowers LLM Agents to read, analyze, and manage lengthy documents intelligently, mimicking human-like comprehension and navigation capabilities.
Features
Document Navigation: Navigate through document sections, headings, and content structure
Content Extraction: Extract and summarize specific document sections
Search & Query: Find specific content within documents using intelligent search
Multi-format Support: Currently supports Markdown (.md) files, with planned support for PDF and other formats
MCP Integration: Seamless integration with MCP-compatible LLMs and applications
Related MCP server: Zileo Docs
Architecture
DocNav follows a modular, extensible architecture:
Core MCP Server: Main server implementation using the MCP protocol
Document Processors: Pluggable processors for different file types
Navigation Engine: Handles document structure analysis and navigation
Content Extractors: Extract and format content from documents
Search Engine: Provides search and query capabilities across documents
Installation
Prerequisites
Python 3.10+
uv package manager
Setup
Clone the repository:
git clone https://github.com/shenyimings/DocNav-MCP.git
cd DocNav-MCPInstall dependencies:
uv syncUsage
Starting the MCP Server
uv run server.pyConnect to the MCP server
{
"mcpServers": {
"docnav": {
"command": "{{PATH_TO_UV}}", // Run `which uv` and place the output here
"args": [
"--directory",
"{{PATH_TO_SRC}}",
"run",
"server.py"
]
}
}
}Available Tools
load_document: Load a document for navigation and analysisArgs:
file_path(path to document file)Returns: Success message with auto-generated document ID
get_outline: Get document outline/table of contentsArgs:
doc_id(document identifier),max_depth(max heading depth, default 3)Returns: Formatted document outline
Tip: Use first after loading a document to understand structure
read_section: Read content of a specific document sectionArgs:
doc_id(document identifier),section_id(e.g., 'h1_0', 'h2_1')Returns: Section content with subsections
search_document: Search for specific content within a documentArgs:
doc_id(document identifier),query(search term or phrase)Returns: Formatted search results with context
navigate_section: Get navigation context for a sectionArgs:
doc_id(document identifier),section_id(section to navigate to)Returns: Navigation context with parent, siblings, children
list_documents: List all currently loaded documentsReturns: List of loaded documents with metadata
get_document_stats: Get statistics about a loaded documentArgs:
doc_id(document identifier)Returns: Document statistics and structure info
remove_document: Remove a document from the navigatorArgs:
doc_id(document identifier)Returns: Success or error message
Example Usage
# Load a document
result = await tools.load_document("path/to/document.md")
# Get document outline
outline = await tools.get_outline(doc_id)
# Get specific section content
section = await tools.read_section(doc_id, section_id)
# Search within document
results = await tools.search_document(doc_id, "search query")Development
Project Structure
docnav-mcp/
--- server.py # Main MCP server
--- docnav/
------- __init__.py # Package initialization
------- models.py # Data models
------- navigator.py # Document navigation engine
------- processors/
------- __init__.py # Processor package
------- base.py # Base processor interface
------- markdown.py # Markdown processor
--- tests/
------- ... # Test filesDevelopment Guidelines
See CLAUDE.md for detailed development guidelines including:
Code quality standards
Testing requirements
Package management with uv
Formatting and linting rules
Adding New Document Processors
Create a new processor class inheriting from
BaseProcessorImplement the required methods:
can_process,process,extract_section,searchRegister the processor in the
DocumentNavigatorAdd comprehensive tests
Running Tests
# Run all tests
uv run tests/run_tests.pyCode Quality
# Format code
uv run --frozen ruff format .
# Check linting
uv run --frozen ruff check .
# Type checking
uv run --frozen pyrightRoadmap
Complete Markdown processor implementation
Add PDF document support (PyMuPDF)
Improve test coverage and quality
Implement advanced search capabilities
Add document summarization features
Support for additional document formats (DOCX, TXT, etc.)
Performance optimizations for large documents
Caching mechanisms for frequently accessed documents
Add persistent storage for loaded documents
Contributing
Fork the repository
Create a feature branch
Follow the development guidelines in CLAUDE.md
Add tests for new functionality
Submit a pull request
License
This project is licensed under the Apache-2.0 License - see the LICENSE file for details.
Support
For issues and questions:
Open an issue on GitHub
Check the documentation in CLAUDE.md
Review existing issues and discussions
Available Tools
8 toolsget_document_statsC
Get statistics about a loaded document.
Args:
doc_id: Document identifier
Returns:
Document statistics and structure info
Inputs: doc_id (required). Returns: result
get_outlineA
Get document outline/table of contents.
Tips: First use this tool to understand document structure after you load a document.
Args:
doc_id: Document identifier
max_depth: Maximum heading depth to include, defaults to 3
Returns:
Formatted document outline
Inputs: doc_id (required), max_depth. Returns: result
list_documentsA
List all currently loaded documents.
Returns:
List of loaded documents with their metadata
Inputs: no named parameters. Returns: result
load_documentB
Load a document for navigation and analysis.
Args:
file_path: Path to the document file
Returns:
Success message with auto-generated document ID
Inputs: file_path (required). Returns: result
read_sectionA
Read content of a specific document section.
Args:
doc_id: Document identifier
section_id: Section ID from outline (e.g., 'h1_0', 'h2_1')
Returns:
Section content with subsections
Inputs: doc_id (required), section_id (required). Returns: result
remove_documentC
Remove a document from the navigator.
Args:
doc_id: Document identifier (UUID)
Returns:
Success or error message
Inputs: doc_id (required). Returns: result
search_documentC
Search for specific content within a document.
Args:
doc_id: Document identifier
query: Search term or phrase
Returns:
Formatted search results with context
Inputs: doc_id (required), query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: list_documents enumerates loaded docs, load_document/remove_document manage the document lifecycle, get_outline provides structure, navigate_section gives context, read_section extracts content, search_document finds text, and get_document_stats offers metadata. An agent can easily differentiate them based on their specific actions and targets.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_documents, load_document, get_outline, and navigate_section. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions across the eight tools.
With 8 tools, this server is well-scoped for document navigation and analysis, covering core operations like loading, listing, navigating, reading, searching, and removing documents, along with metadata and outline retrieval. Each tool earns its place without redundancy, making the count ideal for the domain.
The tool set provides complete CRUD/lifecycle coverage for document navigation: load_document (create), list_documents (read), remove_document (delete), and operations for analysis (get_outline, navigate_section, read_section, search_document, get_document_stats). There are no obvious gaps, ensuring agents can perform all essential tasks without dead ends.
Maintenance
Related MCP Connectors
MCP server for agentverse documentation, generated by doc2mcp.
MCP server for langchain documentation, generated by doc2mcp.
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search, deep-read, and build knowledge bases from Markdown, PDF, DOCX, and PPTX documents via MCP tools for retrieval, document navigation, and ingestion.23 npm652MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for indexing, semantic search, and generation of multi-format documents. Exposes 13 tools over JSON-RPC 2.0 so an LLM can search your local PDF, Excel, and Word files, and create or edit Excel and Word documents.AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides document analysis capabilities to LLM applications, including extraction, chunking, summarization, and semantic search for PDF, DOCX, and plaintext documents.-
- AlicenseNot gradedqualityDmaintenanceMCP server that allows AI agents to read, search, summarize, and answer questions about local PDF, DOCX, XLSX, and TXT files through five tools.MIT