Yuque MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUQUE_BASE_URL | No | Base URL for privately deployed Yuque instance. Defaults to https://www.yuque.com/api/v2. | |
| YUQUE_PERSONAL_TOKEN | Yes | Your Yuque personal access token. Can also be passed as --token CLI argument. |
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_get_userA | Get current authenticated user information |
| yuque_list_booksB | List all books (知识库) for the current user |
| yuque_get_bookB | Get a specific book (知识库) by ID or namespace |
| yuque_create_bookB | Create a new book (知识库) for the current user |
| yuque_update_bookC | Update a book (知识库) |
| yuque_list_docsA | List all documents in a repo/book |
| yuque_get_docB | Get a specific document with full content |
| yuque_create_docA | Create a new document in a repo/book |
| yuque_update_docC | Update an existing document |
| yuque_get_tocB | Get the table of contents (TOC) for a repo/book |
| yuque_update_tocA | Update the table of contents (TOC) for a repo/book. The toc_data must be a single-operation JSON object (not an array). Required fields: "action" (e.g. "appendNode"), "action_mode" ("child" or "sibling"), "target_uuid" (empty string for root level). For new nodes: include "type" ("TITLE" or "DOC") and "title". To move existing nodes: use "node_uuid" instead. Example: {"action":"appendNode","action_mode":"child","target_uuid":"","type":"TITLE","title":"New Section"} |
| yuque_searchC | Search for documents or repos in Yuque |
| yuque_list_notesB | List all notes (小记) for the current user with pagination |
| yuque_get_noteB | Get a specific note with full content |
| yuque_create_noteB | Create a new note (小记) |
| yuque_update_noteC | Update an existing note |
| yuque_get_resourceA | Read a structured resource view from a Yuque document. Currently resource_type only supports board; pass the raw resource_id, not board://. |
| yuque_create_resourceB | Create a structured resource in a Yuque document. Currently resource_type only supports board: mindmap, flowchart, or architecturediagram. |
| yuque_update_resourceA | Update a structured resource in a Yuque document. Currently resource_type only supports board; provide exactly one of text or dsl. |
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 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.