Yuque MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUQUE_TOKEN | Yes | Your Yuque API token |
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 user information) |
| yuque_get_reposB | 获取知识库列表 (List knowledge repositories) |
| yuque_get_docsA | 获取文档列表 (List documents in a repository) |
| yuque_get_docC | 获取文档详情 (Get document details) |
| yuque_create_docC | 创建新文档 (Create new document) |
| yuque_update_docC | 更新文档 (Update existing document) |
| yuque_delete_docC | 删除文档 (Delete document) |
| yuque_search_docsC | 搜索文档 (Search documents) |
| yuque_create_repoC | 创建知识库 (Create knowledge repository) |
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 9 tools
Each tool targets a distinct action and resource (doc vs repo vs user), with no ambiguous overlaps.
All tools follow a consistent 'yuque_verb_noun' snake_case pattern, making the set predictable.
9 tools is well-scoped for a knowledge base server, covering essential operations without being overwhelming.
Doc CRUD is fully covered, but repo management lacks get, update, and delete, creating a minor gap.