A
licenseNot graded
qualityC
maintenanceEnables MCP clients to access and read mdbook documentation, including structure, content, and search.
8
3
MIT
mofox-docs-mcp
Related Servers
Alternatives to mofox-docs-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
- AlicenseAqualityBmaintenanceThis server crawls documentation sites and provides search and page-retrieval tools through MCP, enabling users to query indexed documentation content.4MIT
- FlicenseAqualityDmaintenanceProvides AI assistants with real-time access to the AGNO framework documentation by enabling them to browse, search, and fetch documentation pages. This server allows users to query information about AGNO's Agents, Teams, and Workflows directly through MCP-compatible clients.16-
- FlicenseAqualityCmaintenanceEnables MCP-compatible clients to search and read local markdown documentation, allowing agents to retrieve relevant doc snippets or full files by path.2-
- AlicenseNot gradedqualityAmaintenanceA generic, configurable MCP server that makes any MkDocs documentation site searchable and explorable from MCP clients.MIT
TDQS
A4.6/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct role: search_docs finds relevant docs by keywords, list_docs provides browsable pagination, and get_doc returns complete content for a specific doc. There is no meaningful overlap between them.
Naming Consistency5/5
All tool names follow a clean verb_noun pattern: search_docs, list_docs, and get_doc. The slight singular/plural difference between docs and doc is natural and does not create confusion.
Tool Count5/5
With only three tools, the server covers the core documentation workflow of search, browse, and retrieve without redundancy. This is an appropriately minimal surface for a docs-focused server.
Completeness5/5
The tools form a complete documentation lifecycle: discover content through search and listing, then fetch the full text via get_doc. There are no obvious gaps, as the server's documented purpose is fully supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues