A
licenseNot graded
qualityC
maintenanceEnables AI assistants to interact with Yuque (语雀) platform through MCP protocol, supporting knowledge base management, document operations, search, and team collaboration features.
10
MIT
yuque-mcp
by wwwwujl
Related Servers
Alternatives to yuque-mcp
No user-submitted related servers found.
Related Servers
- 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).-
- AlicenseBqualityCmaintenanceEnables interaction with Yuque (语雀) knowledge base platform through their API. Supports document management, search, and repository operations including creating, reading, updating, and deleting documents in multiple formats.919 npm3MIT
- AlicenseBqualityDmaintenanceEnables access to Yuque (语雀) documentation through cookie-based authentication, supporting document retrieval, search, TOC navigation, and content management from knowledge bases via URL or namespace.4358 npm4MIT
Yuque MCP Serverofficial
AlicenseBqualityCmaintenanceMCP server for Yuque (语雀) that exposes your knowledge base to AI assistants through the Model Context Protocol.19358 npm245MIT- AlicenseBqualityDmaintenanceEnables reading Yuque documents, listing knowledge base docs, and converting source content to Markdown via MCP. Supports session cookie authentication and optional Playwright rendering.31MIT
TDQS
C2.9/5.0
Scored across 28 tools
Disambiguation3/5
Several convenience wrappers overlap with core tools: yuque_get_repository_overview duplicates yuque_get_repo_toc, yuque_create_document_with_toc overlaps yuque_create_doc, and yuque_search_and_read overlaps yuque_search_docs. These pairs create ambiguity about which tool to select for a given task.
Naming Consistency4/5
All tools follow a clear yuque_ verb_noun convention in snake_case. Minor deviations like add/remove vs create/delete for group users and composite suffixes (with_toc, from_file) are still readable and predictable.
Tool Count2/5
With 28 tools, the server exceeds the typical comfortable range and includes several redundant composite wrappers that inflate the count. The core domain could be covered with fewer tools, though the breadth of resources (users, groups, repos, docs) partially justifies the number.
Completeness5/5
The tool set covers full lifecycle for groups, repos, and docs: create, read, update, delete, list, and search operations are all present, plus membership management. No obvious critical gaps hinder typical workflows, and file-based document updates add useful functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues