docsbook-mcp
OfficialRelated Servers
Alternatives to docsbook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server that exposes 39 tools for GitBook API automation, enabling AI agents to manage documentation, change requests, reviews, and Git Sync.39145 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Nyxdoc, a document system where humans and external agents collaborate on documents with version history, agent to-dos, and workspace permissions.MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, mints agent keys, and shares a unified tool library across multiple AI harnesses.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, write, and maintain documentation through an MCP server, providing tools for asking questions, generating docs, checking drift, and exploring knowledge graph.15 npmMIT
- AlicenseBqualityCmaintenanceMCP server to publish HTML/Markdown docs, upload assets, and reply to stakeholder comments on uselink.app directly from AI tools like Claude and Cursor.346 npmMIT
- FlicenseNot gradedqualityBmaintenanceUniversal dynamic MCP server for Frappe & ERPNext v16, exposing 36 tools, resources, prompts, SSE transport, and real-time webhooks to manage 816+ DocTypes.-
TDQS
Scored across 62 tools
Most tools are clearly distinct, but the doc_search_* family (doc_search_text, doc_grep, doc_search_paths, doc_search_by_anchor) and the general search_docs overlap in function, which could cause misselection. The analytics and workspace tools are well-separated.
The majority of tools follow a clear verb_noun pattern (get_, list_, update_, create_, delete_, set_, test_). However, the doc_* tools (doc_outline, doc_breadcrumbs, doc_neighbors) deviate by using a prefix instead of a leading verb, though they remain readable and predictable.
62 tools is extreme for an MCP server. Even for a feature-rich documentation platform, this exceeds reasonable scope and will overwhelm agents with too many options, making selection harder.
The tool set covers many features but has significant gaps: no delete_workspace, no delete_doc, no register_webhook (only unregister), and no general list_translations (only pending). These missing lifecycle operations create dead ends and prevent full workflows.