Overview
Features
Docy MCP Server for documentation access
A FastMCP v2-based MCP server enabling LLMs to search and retrieve content from documentation websites by scraping with crawl4ai.
Hot-reloadable documentation sources
Configure sources via the .docy.urls file and edit on-the-fly; changes are reflected without restarting.
Intelligent caching with diskcache and TTL
Caches documentation content with a configurable TTL to reduce latency and external requests; supports persistent disk-based caching.
Hybrid caching rules for dynamic sources
When using .docy.urls, the list of sources is not cached, enabling hot-reload behavior while page content remains cached.
Documentation tooling: discover and fetch content
Tools include list_documentation_sources_tool, fetch_documentation_page, and fetch_document_links to explore and retrieve docs.
MCP integration with Claude Code and IDEs
Designed to work seamlessly with Claude Code, VS Code, and other MCP-enabled tools for documentation-based guidance.
Flexible deployment and transport
Run via uv, pip, or Docker, with transport options including SSE and stdio.
Local development and debugging support
Provides a local API (http://127.0.0.1:6274) and MCP inspector for debugging and testing.
Who Is This For?
- AI developers:Integrate Docy into MCP workflows to give LLMs direct, real-time access to documentation across configured sources.
- MCP-enabled tool developers:Configure and host Docy to supply documentation content to Claude Code, VS Code, and other MCP clients.
- Teams and organizations:Share documentation sources via a central .docy.urls file with hot-reload and centralized caching for consistent docs.




