yuque
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUQUE_HOST | No | Default Yuque host for short-path URL completion | https://www.yuque.com |
| YUQUE_SESSION | Yes | Yuque session cookie (_yuque_session value) | |
| YUQUE_RENDER_MODE | No | Rendering mode: auto, off, or force | auto |
| YUQUE_BROWSER_CHANNEL | No | Playwright browser channel, e.g. chrome | |
| YUQUE_CHROMIUM_EXECUTABLE | No | Absolute path to a Chromium/Chrome executable |
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_readA | Read a Yuque document by URL. Returns the full rendered content. |
| yuque_list_docsB | List all documents in a Yuque repository |
| yuque_read_markdownA | Read a Yuque document by URL using Yuque Lake/API source content and convert it to readable Markdown with tables, PlantUML, Mermaid, code blocks, images, links, and board summaries. |
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 3 tools
The three tools are distinct: one lists documents, and two read documents in different formats. However, the two read tools have overlapping purposes (both read a document by URL), which could cause minor confusion.
All tools share a 'yuque_' prefix and use verb_noun for most, but 'yuque_read' lacks a noun suffix, creating slight inconsistency with 'yuque_list_docs' and 'yuque_read_markdown'.
With only 3 tools, the server is severely under-scoped for a platform like Yuque, which typically requires many more operations (create, update, delete, etc.).
The server only provides read and list functionality, missing essential CRUD operations. It is extremely incomplete for the Yuque domain.