A
licenseNot graded
qualityD
maintenanceA self-hosted MCP server that provides up-to-date documentation for enterprise and development tools directly to AI coding assistants like Claude Code and Cursor.
MIT
fumadocs-mcp
by k4cper-g
Related Servers
Alternatives to fumadocs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.19 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to access up-to-date documentation for Python libraries like LangChain, LlamaIndex, and OpenAI through dynamic fetching from official sources.1MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server that indexes documentation from various sources and makes it searchable by AI assistants via the Model Context Protocol and REST API.17 npm78Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.MIT
- AlicenseAqualityDmaintenanceAn MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.54MIT
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: get_component retrieves UI component details, get_page fetches full page content, get_setup_guide provides framework-specific setup instructions, list_topics browses documentation sections, and search_docs performs keyword searches. There is no overlap in functionality, making tool selection straightforward for an agent.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case: get_component, get_page, get_setup_guide, list_topics, and search_docs. The verbs (get, list, search) are appropriately descriptive and uniform, creating a predictable and readable naming convention throughout the set.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of accessing Fumadocs documentation. Each tool serves a specific and necessary function (e.g., retrieving components, pages, setup guides, browsing topics, and searching), with no redundancy or missing core operations, making the count ideal for the domain.
Completeness5/5
The tool set provides complete coverage for documentation access: it supports retrieving specific components and pages, getting setup instructions, browsing topics, and searching. This covers all typical user workflows (lookup, navigation, and discovery) without obvious gaps, ensuring agents can handle common documentation tasks effectively.
Maintenance
ActivityInactive
ResponsivenessNo issues