yuque-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUQUE_TOKEN | Yes | Yuque API token | |
| YUQUE_ENDPOINT | No | Yuque API endpoint | https://www.yuque.com/api/v2/ |
| YUQUE_FILE_ROOT | No | Root directory for file operations | |
| YUQUE_TIMEOUT_MS | No | Timeout in milliseconds | 10000 |
| YUQUE_ALLOW_WRITE | No | Enable write operations | false |
| YUQUE_MAX_RETRIES | No | Maximum retries for read-only operations | 2 |
| YUQUE_ALLOW_DELETE | No | Enable delete operations | false |
| YUQUE_FILE_MAX_BYTES | No | Maximum file size in bytes | 1048576 |
| YUQUE_WRITE_GROUP_ALLOWLIST | No | Comma-separated group login allowlist for writes | |
| YUQUE_FILE_ALLOWED_EXTENSIONS | No | Allowed file extensions | .md,.markdown,.txt |
| YUQUE_WRITE_NAMESPACE_ALLOWLIST | No | Comma-separated namespace allowlist for writes | |
| YUQUE_DELETE_NAMESPACE_ALLOWLIST | No | Comma-separated delete allowlist targets |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yuque_get_current_userA | Get current Yuque user profile. |
| yuque_list_groupsA | List groups for current user or a provided login. |
| yuque_get_groupC | Get a group by login or id. |
| yuque_create_groupC | Create a new Yuque group. |
| yuque_update_groupC | Update an existing Yuque group. |
| yuque_delete_groupC | Delete a Yuque group (requires confirmation). |
| yuque_list_group_usersB | List users in a Yuque group. |
| yuque_add_group_userC | Add or update a user membership in a Yuque group. |
| yuque_remove_group_userB | Remove a user from a Yuque group. |
| yuque_list_reposC | List repos under a user or group. |
| yuque_get_my_repositoriesB | Get current user and repositories in one call. |
| yuque_get_repoC | Get a repo by namespace. |
| yuque_create_repoB | Create a new Yuque repository under user or group. |
| yuque_update_repoC | Update an existing Yuque repository. |
| yuque_delete_repoB | Delete a Yuque repository (requires confirmation). |
| yuque_get_repo_tocC | Get repo TOC entries. |
| yuque_get_repository_overviewA | Get repository details and TOC in one call. |
| yuque_list_docsA | List docs under a repo namespace with pagination. |
| yuque_get_docA | Get a single doc by namespace and either slug or doc_id. |
| yuque_search_docsB | Client-side search over listed docs by title, slug, and description. |
| yuque_create_docC | Create a new Yuque doc. |
| yuque_create_document_with_tocC | Create a document and attach it to TOC in one call. |
| yuque_update_docC | Update an existing Yuque doc by slug or doc_id. |
| yuque_delete_docA | Delete a Yuque doc by namespace and slug/doc_id (requires confirmation). |
| yuque_update_tocC | Update Yuque repository TOC nodes. |
| yuque_search_and_readA | Search docs and optionally read the first hit in one call. |
| yuque_create_doc_from_fileC | Create document from local file content and attach to TOC. |
| yuque_update_doc_from_fileC | Update document body from local file content. |
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 28 tools
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.
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.
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.
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.