Yuque MCP Server
OfficialRelated Servers
Alternatives to Yuque MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Yuque (语雀) platform through MCP protocol, supporting knowledge base management, document operations, search, and team collaboration features.10MIT
- FlicenseBqualityDmaintenanceA Model-Context-Protocol server that integrates with Yuque (语雀) knowledge base platform, allowing AI models to create, read, update, and delete documents, search content, and retrieve analytics data through defined tools.1469-
- AlicenseBqualityDmaintenanceExposes Yuque knowledge base to AI assistants for searching, creating, and managing documents and books via the Model Context Protocol.25444 npm1MIT
- AlicenseNot gradedqualityCmaintenance本地语雀 MCP 服务器,通过浏览器登录态访问语雀,支持读取、创建和编辑文档,具有知识库白名单和只读模式等安全特性。2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to read and write Yuque documents through MCP, providing tools for managing user info, knowledge bases, and documents with dual authentication modes (official API or cookie).-
- AlicenseBqualityDmaintenanceA Model Context Protocol service that enables AI agents to securely access and operate Yuque knowledge bases via the Yuque OpenAPI.14Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a specific resource type and action (e.g., create, get, list, update) with clear naming prefixes like yuque_create_book, yuque_get_doc, etc. No two tools have overlapping purposes, making selection unambiguous.
All tools follow a consistent 'yuque_verb_noun' pattern using lowercase snake_case. The verbs are uniform (create, get, list, update) and the nouns correspond to resource types (book, doc, note, resource, toc), ensuring predictability.
With 19 tools covering books, docs, notes, resources, TOC, search, and user info, the count is on the higher side but still reasonable for a platform with multiple resource types. Each tool serves a distinct purpose without redundancy.
The toolset lacks delete operations for any resource type (books, docs, notes, resources, TOC). There is also no listing for resources or TOC items. These gaps prevent full lifecycle management and may cause agent failures when cleanup is needed.