Yuque MCP Serverofficial
A
licenseB
qualityD
maintenanceMCP server for Yuque (语雀) that exposes your knowledge base to AI assistants through the Model Context Protocol.
19
307 npm
249
MIT
Yuque MCP Server
by HenryHaoson
Related Servers
Alternatives to Yuque MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol service that enables AI agents to securely access and operate Yuque knowledge bases via the Yuque OpenAPI.14Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Yuque (语雀) platform through MCP protocol, supporting knowledge base management, document operations, search, and team collaboration features.10MIT
- AlicenseBqualityDmaintenanceExposes Yuque knowledge base to AI assistants for searching, creating, and managing documents and books via the Model Context Protocol.25307 npm1MIT
- 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).2-
- AlicenseBqualityDmaintenanceAn enhanced MCP server for the Yuque knowledge base that provides advanced document management, directory tree navigation, and structural adjustment capabilities. It enables AI assistants to manage complex content hierarchies, move nodes, and execute general OpenAPI requests within the Yuque platform.359 npmMIT
TDQS
B3.4/5.0
Scored across 14 tools
Disambiguation4/5
Most tools have distinct purposes, such as create_doc, delete_doc, get_doc, and update_doc for document CRUD operations, and get_current_user for user info. However, there is some overlap among the statistics tools (e.g., get_group_book_statistics, get_group_doc_statistics, get_group_member_statistics, get_group_statistics), which could cause confusion as they all retrieve similar team-related data but with slightly different scopes. Descriptions help clarify, but the boundaries are not perfectly clear.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Examples include create_doc, get_doc, update_doc, get_user_repos, and search. All tools adhere to this convention, making them predictable and easy to understand at a glance.
Tool Count5/5
With 14 tools, the count is well-scoped for a Yuque (knowledge base) MCP server. It covers core operations like document management (CRUD), user and repository info, and statistics, without being overwhelming. Each tool appears to serve a specific purpose, justifying its inclusion in the set.
Completeness4/5
The tool set provides comprehensive coverage for document management (create, get, update, delete, list, search) and user/repository info, with added statistics for teams. Minor gaps exist, such as no tools for managing knowledge repositories (e.g., create_repo, delete_repo) or handling comments/likes on documents, but agents can likely work around these with the available tools for core workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues