Reported issues for yuque-mcp

Pod holds 19 of 22 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to yuque-mcp.

Most discussed

[Feature] 需要能读到文档里面的图片链接

Problem or Motivation

yuque-mcp 获取不到文档里面的图片，甚至连图片链接都看不到，做修改总是会把原内容破坏。

Proposed Solution

markdown内容里面如实提现图片链接

Acceptance Criteria

No response

Alternatives Considered

No response

Additional Context

No response

Read the thread · 2026-07-28 · open · external user · 2 comments

[Bug] 限流是否过于严格了？

Version

0.1.13

Steps to Reproduce

我使用的claude code，我用这个查看我的知识库，直接返回too many request ，我很好奇，你们是如何定义限流的？你们自己开放mcp，但又无法使用？出了token，但又只允许会员使用，你知道我为什么特意开了会员么？就是为了通过这个mcp把我的文档迁移到notion，因为notion这个功能是免费的，在AI时代，这种基础AI功能居然收费？

Expected Behavior

想做企业版，就不要开放给普通用户，开放给普通用户又一大堆收费功能

Actual Behavior

一直显示限流 too many request

Environment

claude

Read the thread · 2026-05-01 · closed · external user · 2 comments

[Feature] 能否支持多token配置

Problem or Motivation

现在是一个知识库，一个token，这样就需要配置多个mcp，使用时会每个mcp都调用一次，不仅配置麻烦，使用也麻烦

Proposed Solution

建议支持 { "知识库id":"token" } 这样的配置，这样配一个mcp就行了，并且能通过链接中的id自动找到对应的token

Alternatives Considered

No response

Additional Context

No response

Read the thread · 2026-04-11 · open · external user · 6 comments

Node.js v24 下启动报错 ERR_IMPORT_ATTRIBUTE_MISSING

问题描述

在 Node.js v24.14.0 环境下，通过 npx -y yuque-mcp 启动 MCP 服务时报错：

node:internal/modules/esm/assert:88
        throw new ERR_IMPORT_ATTRIBUTE_MISSING(url, 'type', validType);
              ^

TypeError [ERR_IMPORT_ATTRIBUTE_MISSING]: Module "file:///root/.npm/_npx/f9d3fcb52165ad9d/node_modules/yuque-mcp/package.json" needs an import attribute of "type: json"
    at validateAttributes (node:internal/modules/esm/assert:88:15)
    at defaultLoadSync (node:internal/modules/esm/load:164:3)

Read the thread · 2026-03-30 · closed · external user · 7 comments

[Bug] The Yuque MCP service can only export images, not Mermaid text.

Version

v0.1.9

Steps to Reproduce

Config Yuque map server in cursor
export Yuqu doc with Mermaid flowchart
only SVG export, no Mermaid code(text)

Expected Behavior

I expect give use options, and use can export docs with Mermaid flowchart code

Actual Behavior

I use yuque mcp server in Cursor

Environment

Read the thread · 2026-03-22 · closed · external user · 2 comments

[BUG] 更新文档功能，查看时，语雀的APP没有实时更新文档，但看语雀网页端，又是已经更新了的

Read the thread · 2026-03-05 · closed · external user · 2 comments

[BUG] 安装选择qoder客户端，提示不支持

Describe the bug 安装选择qoder客户端，提示不支持

To Reproduce Steps to reproduce the behavior:

Run command 'npx yuque-mcp install --client=qoder --token=XXX'
See error

Expected behavior

❌ Unknown client: "qoder". Supported clients: claude-desktop, vscode, cursor, windsurf, cline, trae

Error messages

❌ Unknown client: "qoder". Supported clients: claude-desktop, vscode, cursor, windsurf, cline, trae

Environment:

OS: [Windows]
Node.js version: [e.g. 18.0.0]
Packag

Read the thread · 2026-03-02 · closed · external user · 2 comments

所以想要使用语雀的mcp，要开通超级会员是吗？

我看只有超级会员才能用生成token！！！

Read the thread · 2026-02-27 · closed · external user · 4 comments

Most recent

[Bug] 你妈的头一次见到获取token需要开会员的平台绝了

Version

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

Read the thread · 2026-08-20 · open · external user · 0 comments

[Bug] npm v1.0.0 does not recognize YUQUE_TOKEN documented on main

Version

1.0.0

Steps to Reproduce

Description

The current README on main recommends using YUQUE_TOKEN:

{
  "env": {
    "YUQUE_TOKEN": "YOUR_TOKEN"
  }
}

However, the latest npm release (yuque-mcp@1.0.0) only recognizes
YUQUE_PERSONAL_TOKEN.
When configured with YUQUE_TOKEN, the MCP server exits during startup,
so the client cannot complete tools/list and no Yuque tools are exposed.
Reproduction
YUQUE_TOKEN=dummy npx -y yuque-mcp@1.0.0
Output:
Error: YUQUE_PERSONAL_T

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/86) · 2026-07-24 · open · external user · 0 comments

### [Bug] yuque_get_resource / yuque_update_resource 参数名错误：发送 src 而非 resource_id，导致 400

## 问题描述

`yuque_get_resource` 和 `yuque_update_resource` 两个工具（board 资源）在调用真实语雀 API 时**必现 400 错误**，无法正常使用，即便传入的 `resource_id` 是刚用 `yuque_create_resource` 创建出来、确定存在的合法 ID。

Tool execution failed: resource_id is required (Bad request — check the parameters)


## 复现步骤

1. 用 `yuque_create_resource` 创建一个 board（mindmap/flowchart 均可），拿到返回的 `board.resource.id`，例如 `abc12`。
2. 立刻用同一个 `resource_id: "abc12"` 调用 `yuque_get_resource`（或 `yuque_update_resource`）。
3. 必现报错 `resource_id is required`。

## 根因定位

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/83) · 2026-07-12 · open · external user · 0 comments

### [Feature] 增加版本管理 MCP 工具

### Problem or Motivation

前 MCP 工具体系中缺少统一的“版本管理”能力，无法方便地查询：
- 当前项目版本
- 历史修改记录
- 文件变更历史
- 版本间差异

这会严重限制 AI 在以下场景中的能力：
- 长期记忆系统
- 项目知识追踪
- AI 辅助开发

目前 Agent 只能依赖零散上下文推断项目状态，难以维护和信任已经构建的知识库，缺少可靠的“版本感知”能力。

### Proposed Solution

建议增加一个专门的版本管理 MCP 工具，用于查询项目当前状态与历史变更信息。

### Alternatives Considered

_No response_

### Additional Context

_No response_

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/64) · 2026-05-19 · open · external user · 1 comment

### [Feature] Need to move existing document (ID: 266482105) to a folder via API

### Problem or Motivation

Document Organization (PENDING)                                                                       
   
  - ⏳ Move to "ai build/" folder (awaiting Yuque support guidance)                                        
  - 📧 Current location: Root level (fully functional)      
                                                                                                           
  ---                                                       
  📞 When Contacting Yuque Supp

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/62) · 2026-04-19 · open · external user · 0 comments

### feat: 小记(notes)支持标签更新、归档与取消归档

## 背景

我长期用语雀小记作为碎片信息的收集箱——随手记录想法、工作备忘、灵感、待办，以及收藏文章链接。

22、23 年我习惯给小记打标签分类，但手动管理标签很快就乱了，标签越来越多却无法有效组织。后来基本放弃了打标签。

最近有了 AI，我想换一个思路：**让 AI 来打标签和管理标签**。AI 能做跨层级关联，把相关小记串起来，比我自己打标签更有结构感。小记打标签是轻量操作，乱就乱，反正归档后就不看了，比重型知识库操作成本低得多。

理想的工作流是：AI 读取小记 → 分析分类 → 打标签 → 归档已处理的，一气呵成。但目前 MCP Server 缺少关键能力，AI 只能做到"分析和写内容"，无法完成打标签和归档的收尾动作。

## 期望支持的功能

### 1. 更新小记标签

**现状**：`yuque_update_note` 只支持更新内容（`body`），不支持更新 `tags` 字段。小记的 `tags` 在 `list_notes` 和 `get_note` 返回中存在，但无法写入。

**期望**：`updateNote` 支持传入 `tags` 参数：

`

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/61) · 2026-04-16 · open · external user · 0 comments

### feat: updateNote API 应支持 body 参数，与 createNote 保持一致

## 背景

在使用 MCP Server 的 `yuque_update_note` 工具时，发现更新小记的 API 参数与创建小记不一致，导致无法用相同方式传入内容。

## 问题

**创建小记** (`POST /api/v2/notes`) 接受 `body` 字段：

```json
{ "body": "# 标题\n\n正文内容" }

更新小记 (PUT /api/v2/notes/{id}) 不接受 body，必须传入 source、html、abstract 三个字段：

{
  "source": "# 标题\n\n正文内容",
  "html": "<h1>标题</h1><p>正文内容</p>",
  "abstract": "# 标题\n\n正文内容"
}

这意味着调用方必须自行将 markdown 转换为 HTML，否则接口返回 html,source,abstract invalid 错误。

尝试过的方案

方案一：直接传 body（失败）

尝试让 updateNote

Read the thread · 2026-04-16 · open · external user · 0 comments

[Feature] does Yuque MCP service can obtain doc_id review status?

Problem or Motivation

The Yuque MCP service can obtain at least the following for each doc_id (or slug):

review_status: An enum from the API (as-is or mapped to internal enum)
review_checked_at: The last time the status was pulled from Yuque (UTC)
yuque_updated_at / content_version: If the API provides the document's update time or version number
body_hash or etag (if available): Used to determine whether the content has changed relative to the local copy

Proposed Solutio

Read the thread · 2026-04-15 · open · external user · 0 comments

[Feature] 希望支持知识网络的查询

Problem or Motivation

希望支持知识网络的查询，这样可以将语雀当做完整的知识库来做知识管理

Proposed Solution

如上

Alternatives Considered

No response

Additional Context

No response

Read the thread · 2026-04-14 · open · external user · 0 comments

[Bug] 限流不能自动恢复

Version

0.1.13

Steps to Reproduce

⏺ yuque-mcp - yuque_get_doc (MCP)(repo_id: "uxx/xxx", doc_id: 2xxx) ⎿ Error: Tool execution failed: Too Many Requests (Rate limited — too many requests, try again later)

Expected Behavior

可以限流，但要透明

Actual Behavior

限流不能自动恢复，也不透明

Environment

Read the thread · 2026-04-05 · closed · external user · 1 comment

[BUG] tools/call 方法在 stdio 模式下不响应（create_doc, update_doc 等工具）

问题描述

在使用 stdio 模式与 yuque-mcp 交互时，tools/call 方法的请求没有得到响应。服务器只响应了 initialize 请求，但后续的工具调用请求被忽略。

复现步骤

使用 stdio 模式启动 yuque-mcp：

YUQUE_PERSONAL_TOKEN="xxx" npx yuque-mcp

发送初始化请求 + 工具调用请求：

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"qoder","version":"0.7.1"}}}
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"yuque_create_doc","arguments":{"repo_id":"xxx","title":"测试文档"

[Read the thread](https://github.com/yuque/yuque-mcp-server/issues/32) · 2026-03-15 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/yuque/yuque-mcp-server/issues).

Reported issues for yuque-mcp

Most discussed

[Feature] 需要能读到文档里面的图片链接

Problem or Motivation

Proposed Solution

Acceptance Criteria

Alternatives Considered

Additional Context

[Bug] 限流是否过于严格了？

Version

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

[Feature] 能否支持多token配置

Problem or Motivation

Proposed Solution

Alternatives Considered

Additional Context

Node.js v24 下启动报错 ERR_IMPORT_ATTRIBUTE_MISSING

问题描述

[Bug] The Yuque MCP service can only export images, not Mermaid text.

Version

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

[BUG] 更新文档功能，查看时，语雀的APP没有实时更新文档，但看语雀网页端，又是已经更新了的

[BUG] 安装选择qoder客户端，提示不支持

所以想要使用语雀的mcp，要开通超级会员是吗？

Most recent

[Bug] 你妈的头一次见到获取token需要开会员的平台 绝了

Version

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

[Bug] npm v1.0.0 does not recognize YUQUE_TOKEN documented on main

Version

Steps to Reproduce

Description

尝试过的方案

方案一：直接传 body（失败）

[Feature] does Yuque MCP service can obtain doc_id review status?

Problem or Motivation

Proposed Solutio

[Feature] 希望支持知识网络的查询

Problem or Motivation

Proposed Solution

Alternatives Considered

Additional Context

[Bug] 限流不能自动恢复

Version

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

[BUG] tools/call 方法在 stdio 模式下不响应（create_doc, update_doc 等工具）

问题描述

复现步骤

[Bug] 你妈的头一次见到获取token需要开会员的平台绝了