yuque-mcp-plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUQUE_TOKEN | Yes | Yuque API token. This is required for authentication. | |
| YUQUE_RETRIES | No | Optional number of retries for API requests. | |
| YUQUE_TIMEOUT_MS | No | Optional timeout for API requests in milliseconds. | |
| YUQUE_API_BASE_URL | No | Optional base URL for the Yuque API. | |
| YUQUE_DEFAULT_REPO_ID | No | Optional default repository ID. Takes precedence over YUQUE_DEFAULT_REPO_NAMESPACE. | |
| YUQUE_DEFAULT_REPO_NAMESPACE | No | Optional default repository namespace. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yuque_requestA | Generic Yuque OpenAPI request passthrough for endpoints not wrapped by dedicated tools. |
| yuque_multipart_requestB | Generic Yuque multipart request for upload-style endpoints such as attachment workflows. |
| yuque_helloC | Call the Yuque hello endpoint. |
| yuque_get_userB | Get the current Yuque user. |
| yuque_get_reposC | List Yuque repositories for the current user or a specified user. |
| yuque_list_groupsB | List groups or teams for the current user or a specified user. |
| yuque_get_repoC | Get repository detail. |
| yuque_get_default_repositoryA | Resolve the default Yuque repository using server config or a fallback heuristic. |
| yuque_get_repository_toc_treeB | Get the full repository TOC tree, including nested directories and docs. |
| yuque_get_docsC | List docs in a repository. |
| yuque_get_docC | Get doc detail by doc ID. |
| yuque_create_docB | Create a doc. If parentUuid is provided, the doc is attached under that TOC node. |
| yuque_update_docC | Update an existing doc. |
| yuque_move_documentB | Move a doc or TOC node to another parent by UUID. |
| yuque_create_toc_nodeC | Create a TITLE or LINK node in the repository TOC tree. |
| yuque_delete_toc_nodeC | Delete a TITLE or LINK node from the repository TOC tree. |
| yuque_delete_docC | Delete a doc by ID. |
| yuque_searchD | Search Yuque content. |
| yuque_create_repoD | Create a repository. |
| yuque_update_repoC | Update repository metadata. |
| yuque_delete_repoC | Delete a repository. |
| yuque_update_repository_tocC | Send a raw TOC update payload to the repository TOC API. |
| yuque_list_doc_versionsC | List all versions of a document. |
| yuque_get_doc_versionC | Get a specific document version. |
| yuque_list_group_membersC | List all members of a group or team. |
| yuque_update_group_memberC | Update a group member role. |
| yuque_remove_group_memberC | Remove a member from a group. |
| yuque_group_statsC | Get overall statistics for a group. |
| yuque_group_member_statsC | Get member statistics for a group. |
| yuque_group_book_statsC | Get repository statistics for a group. |
| yuque_group_doc_statsC | Get document statistics for a group. |
| yuque_list_reposC | Alias of yuque_get_repos for compatibility with official naming. |
| yuque_list_docsB | Alias of yuque_get_docs for compatibility with official naming. |
| yuque_get_tocC | Alias of yuque_get_repository_toc_tree for compatibility with official naming. |
| yuque_update_tocC | Alias of yuque_update_repository_toc for compatibility with official naming. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 35 tools
Most tools have distinct purposes targeting specific resources and actions, but there is some ambiguity with aliases like yuque_get_docs/yuque_list_docs and yuque_get_repos/yuque_list_repos, which could cause confusion despite being for compatibility. Additionally, generic tools like yuque_request and yuque_multipart_request overlap in functionality with more specific tools, potentially leading to misselection.
All tools follow a consistent yuque_verb_noun naming pattern using snake_case, with verbs like create, get, update, delete, and list. Aliases are explicitly noted for compatibility but maintain the same structure, ensuring predictability and readability throughout the tool set.
With 35 tools, the count is borderline high for a Yuque API wrapper, as it includes many specific operations and aliases that might feel heavy. While it covers extensive functionality, a more streamlined set could reduce complexity without losing core capabilities, making it slightly over-scoped.
The tool set provides comprehensive CRUD and lifecycle coverage for Yuque's domain, including repositories, documents, TOC nodes, groups, and users. It handles creation, retrieval, updating, deletion, searching, and statistics, with no obvious gaps that would hinder agent workflows, ensuring complete surface coverage.