MCP server for Yuque (语雀) — expose Yuque knowledge base to AI assistants via Model Context Protocol
Yuque MCP server exists for a simple reason — assistants are far more useful when they can act on Yuque directly instead of describing what you should do. MCP server for Yuque (语雀) — expose Yuque knowledge base to AI assistants via Model Context Protocol.
[CI][ci-image]][ci-url] [npm version][npm-image]][npm-url] [npm downloads][download-image]][download-url] [License][license-image]][license-url]
Once Yuque is connected, these are the calls the assistant has available:
Category — ToolUser — yuque_get_userSearch — yuque_searchBooks — yuque_list_booksDocs — yuque_list_docsTOC — yuque_get_tocNotes — yuque_list_notesBoards — yuque_get_resourceYou will need 5 environment variables: YUQUE_TOKEN, YOUR_TOKEN, YUQUE_HOST, YUQUE_PERSONAL_TOKEN, YUQUE_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at yuque-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Yuque's toolset — Category, User, Search and 5 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Category | Tool |
| User | yuque_get_user |
| Search | yuque_search |
| Books | yuque_list_books |
| Docs | yuque_list_docs |
| TOC | yuque_get_toc |
| Notes | yuque_list_notes |
| Boards | yuque_get_resource |
{
"mcpServers": {
"yuque": {
"command": "npx",
"args": ["-y", "yuque-mcp"],
"env": {
"YUQUE_TOKEN": "your-value",
"YOUR_TOKEN": "your-value",
"YUQUE_HOST": "your-value",
"YUQUE_PERSONAL_TOKEN": "your-value",
"YUQUE_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| YUQUE_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
| YUQUE_HOST | Endpoint or connection string the server talks to. | Optional |
| YUQUE_PERSONAL_TOKEN | Credential the server authenticates with. | Yes |
| YUQUE_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.