Feishu User MCP

MCP办公协作

提供方 EthanQC · 包名 feishu-user-plugin

办公协作 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorWindsurf
查看接入方式

飞书用户插件是一个MCP服务器和CLI工具,支持用户身份消息发送、群聊和私聊消息读取、文档操作、日历管理等飞书功能,适用于个人开发者和无管理员权限的场景。

一句话选型结论

按资料字段整理

Feishu User MCP 属于办公协作类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 5 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量5暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

飞书集成JavaScript本地部署MCP服务器用户身份消息协作工具实时事件

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx feishu-user-plugin setup --app-id <APP_ID> --app-secret <APP_SECRET>

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 5 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 5 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Feishu User MCP当前 5 stdio · 本地进程 本地部署 有 2026-05-17
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方EthanQC上游标注的维护方 EthanQC
分类办公协作本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时feishu-user-plugin · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.4 KB
来自项目仓库与上游目录的原文,未做删改

Feishu user plugin - Feishu MCP server+CLI tool

Chinese · English · Docs · CHANGELOG · npm

Feishu/Lark MCP server, covering IM, documents, multi-dimensional tables, knowledge base, cloud space, calendar, task v2, OKR, real-time events.85 Tools · 3-layer Authentication · 9 MCP prompts · MIT licensed · Node ≥ 18.

Compatible with MCP clients such as Claude Code, Codex, cursor, Windsurf, VS Code, Claude Desktop, OpenClaw, etc.

There are two paths for sending messages as a user identity:Feishu Official OAuth Scope im:message.send_as_user(requires creating a self built application and administrator approval), or for this warehouse Cookie+protobuf path(Zero application threshold, run immediately after capturing cookies). This warehouse is no longer physically exclusive, but it is still a convenient option for "individual developers/no administrator privileges/want to quickly try" scenarios.

Compared with the official version (Feishu also released MCP+CLI in 2026)

  • larksuite/lark-openapi-mcp ——Official OpenAPI MCP,⚠ Beta +Last updated on August 2025 (9 months ago), README plaintext does not support file upload and download, nor does it support document editing; 1271 endpoint tools, but only~20 presets are available for default, and the rest have not undergone compatibility testing
  • larksuite/cli ——Official CLI (9.9k stars, active), 17 business domains, 200+commands+24 AI Agent Skills,Supported +messages-send --as user(走 OAuth scope im:message.send_as_user)But CLI form instead of MCP, Using Codex/Cursor/Windsurf requires shell out

When should I use this warehouse:

  • I want to send messages/read P2P private chats as a user, butDo not want/cannot create Feishu self built application(Individual developer/No administrator privileges) - Zero threshold for cookie path
  • Using MCP protocol (Codex/Cursor/Windsurf/VS Code, etc.)+no need for email/approval/HR/meeting minutes and other domains not covered by our warehouse
  • Coexistence of multiple MCP clients and the need for "precise delivery of real-time events across the entire machine" (v1.3.9+machine level WS SSOT)

When to use the officialBusiness system domains such as email/approval/attendance/HR/recruitment/meeting minutes are required; Or there may be an existing Feishu application and an administrator approved OAuth scope, with a preference for official long-term stable paths.

See for a complete and honest comparison docs/COMPARISON.md.

usage```

你:帮我以我身份给王小明发:今天的代码 review 我看完了,有 3 个 nit
Claude:[调用 send_to_user] Sent
``````
你:总结"工程组"群今天 9 点之后的讨论,发个日报到 #日报频道
Claude:[read_messages → 总结 → send_to_group] Sent


## Install```bash
npx feishu-user-plugin setup --app-id  --app-secret
npx feishu-user-plugin oauth         # 拿用户 OAuth UAT
# 重启 Claude Code / Codex

Cookie retrieval (Playwright automatic scanning/VNet manual), creation of Feishu application, detailed configuration of each client docs/AUTH-SETUP.md.

Three layer authentication

Authentication layer credentials coverage capability number of tools
User identity (cookie+protobuf) LARK_COOKIE Send text/images/files/rich text/@/batch as a user 8
Official API (Robot) LARK_APP_ID + LARK_APP_SECRET Group message reading and writing, documents, multidimensional tables, knowledge base, cloud space, calendar, task v2, OKR, contacts, real-time event WS 70+
User OAuth UAT LARK_USER_ACCESS_TOKEN + LARK_USER_REFRESH_TOKEN P2P private chat reading, user chat list; Write document/Bitable/calendar resources with user as owner 2 explicit+full tool UAT first

Three layer independence - configure any layer, corresponding tools are available.

core competency

  • Send a message as you(8) : text/image/file/rich text post/card/batch; Differentiated anchor point - Feishu official API does not have it send_as_user
  • Reading groups and P2P private chats(17) : Group messages/private chats/ merge_forward Auto expand/URL+Feishu document link automatic extraction/External group automatic fallback to UAT
  • Document Ecology(27): Feishu documents (including read_doc_markdown Province~60% token)/Multi dimensional table (500 pieces in bulk)/Knowledge base (including write CRUD)/Cloud space
  • Collaboration tool(21): Calendar (read+write)/Task v2 (including member management)/OKR (read+progress record)/Contact person
  • real-time event(2) Machine level SSOT WS, delivering each event precisely once on the entire machine
  • Diagnosis and Multiple Accounts(4) N profiles automatically switch, write path not switched (to avoid creating resources with incorrect numbers)

Complete tool list+cross domain caveat+usage patterns see docs/TOOLS.md.

9 个 MCP prompts(slash commands)

Prompt Description
/send Sending messages as a user
/reply Read the latest news and reply
/digest Summary of Recent News from Groups/P2P
/search Search for contacts/groups
/doc Search/Read/Create Documents
/table Operate multidimensional tables
/wiki Search Knowledge Base
/drive Cloud Space/Create Folder
/status Check the authentication status of the third layer

Client configuration

Unified environment variables, different configuration file locations and top-level keys:

Client Profile Top level Key
Claude Code ~/.claude.json(Recommended Global)/ .mcp.json mcpServers.feishu-user-plugin
Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) mcpServers.feishu
Codex ~/.codex/config.toml [mcp_servers.feishu-user-plugin]
Cursor .cursor/mcp.json(Project level) mcpServers.feishu
VS Code (Copilot) .vscode/mcp.json servers.feishu(Attention) servers, not mcpServers)
OpenClaw ~/.openclaw/openclaw.json mcp.servers.feishu-user-plugin
Windsurf ~/.codeium/windsurf/mcp_config.json mcpServers.feishu
npx feishu-user-plugin setup                       # Claude Code
npx feishu-user-plugin setup --client codex        # Codex
npx feishu-user-plugin setup --client both         # 都写

Please refer to the complete JSON templates for each client README.en.md MCP Client ConfigurationPlease refer to the detailed installation and certification process docs/AUTH-SETUP.md.

multiple accounts

~/.feishu-user-plugin/credentials.json Support multiple profiles (default+arbitrary attachment), with a single machine configured to cover multiple Feishu accounts/enterprises.```bash
npx feishu-user-plugin list-profiles
npx feishu-user-plugin switch-profile
npx feishu-user-plugin keepalive --all # 跨 profile keepalive


Read path tool failure code `91403` / `1254301` / `1254000` / `99991672` / `HTTP 403` Automatically cross profile retry. Do not automatically switch paths when writing (to avoid creating resources with incorrect numbers). Monotonic coverage: transmission `via_profile: &quot;&quot;` Pin to the specified profile.

see details docs/TOOLS.md &quot;多 profile auto-switch&quot;.

## real-time event

A single process on the machine holds a WS owner lock, which is shared by all MCP processes `events.jsonl`Each event happens exactly once on the entire machine.```bash
mcp call manage_ws_status --action info
mcp call manage_ws_status --action claim --force true

Default subscription [&quot;im.message.receive_v1&quot;]To subscribe to approval/calendar/VC and other events, edit credentials.json::profiles[].eventsAnd then manage_ws_status(action=reconfig) Do not restart and re subscribe.

WSClient that only supports feishu.cn - Lark International Edition (Lark. com) is currently not supported.

Known limitations

  • Cookie lifespan12-24 hours without heartbeat expiration, need to log in to feishu.cn again to retrieve cookies
  • Protocol changesThe cookie+protobuf layer depends on the protocol of the Feishu web client, and Feishu updates may become invalid (robot capabilities are not affected)
  • cardThe cookie channel cannot send cards to the server, but the robot channel can send them
  • Lark International EditionReal time event WS is not supported
  • unrealized:search_messages、 Md → wiki synchronization (see details) ROADMAP.md)

document

Document Role
docs/TOOLS.md Detailed Tools+Cross Domain Caveat+Usage Patterns
docs/AUTH-SETUP.md Installation/Three layer authentication/Cookie scraping/OAuth scopes
docs/TROUBLESHOOTING.md Error codes and diagnosis
docs/RELEASING.md Release process+Team kills synchronization+Announcement rules
docs/REFACTOR-NOTES.md Document Responsibility Matrix
docs/CREDENTIALS-FORMAT.md Voucher schema
docs/TESTING-METHODOLOGY.md Testing method
CONTRIBUTING.md Contribution process (bilingual in Chinese and English)
ROADMAP.md Roadmap (forward only)
CHANGELOG.md Historical changes

Complete docs/index:docs/README.md.

contribution

Issues/PRs are welcome. Check before submitting CONTRIBUTING.md.

Fei Shu changed the protocol and caused the function to crash - simply open an issue with an error log.

Privacy/Privacy

The MCP server running locally retains credentials on the user's local machine, does not report telemetry, and does not communicate with the plugin author's backend. The complete text can be found at PRIVACY.md.

  • collectThe plugin itself does not collect any data;LARK_COOKIE / LARK_APP_ID / LARK_APP_SECRET / LARK_USER_ACCESS_TOKEN / LARK_USER_REFRESH_TOKEN All user initiated configurations are sourced from their own Feishu/Lark accounts
  • handleOnly process messages/documents/multidimensional tables/knowledge bases/cloud spaces/calendars/tasks/OKRs/contacts actively requested by users through MCP tools, without retention or analysis
  • storage:~/.feishu-user-plugin/credentials.json(mode 0600); Optional event log ~/.feishu-user-plugin/events.jsonl(10 MB/20 MB automatic rotation)
  • third partyOnly communicate with the user's own Feishu tenant and the AI client running by the user, without CDN/analysis/error reporting
  • retain: Full user control;rm -rf ~/.feishu-user-plugin &amp;&amp; npm uninstall -g feishu-user-plugin Clear immediately
  • contact:GitHub IssuesAdd security issues before the issue title [security]

A locally-run MCP server. Credentials stay on the user's machine; no telemetry, no phone-home. Full text at PRIVACY.md.

  • Collected: nothing by the plugin itself; the five LARK_* envs are supplied by the user from their own Feishu / Lark account
  • Processed: only the messages / docs / bitable / wiki / drive / calendar / tasks / OKR / contacts the user explicitly requests via MCP tool calls
  • Stored: ~/.feishu-user-plugin/credentials.json (mode 0600); optional event log at ~/.feishu-user-plugin/events.jsonl
  • Third-party: only the user's own Feishu tenant and the AI client the user runs (Claude Code / Codex / Cursor / etc.)
  • Retention: entirely user-controlled; rm -rf ~/.feishu-user-plugin &amp;&amp; npm uninstall -g feishu-user-plugin removes everything
  • Contact: GitHub Issues; security disclosures with [security] prefix in the title

License

MIT

Acknowledgments

  • cv-cat/LarkAgentX ——Research on Early Feishu Web Protocol (Python)
  • cv-cat/OpenFeiShuApis ——Research on the underlying API
  • Model Context Protocol ——MCP standard+Anthropic/PulseMCP/GitHub/Stacklok co maintained registry

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Feishu User MCP 怎么安装?

在客户端按下面的安装命令接入:npx feishu-user-plugin setup --app-id <APP_ID> --app-secret <APP_SECRET>。对应的包名是 feishu-user-plugin。装完在客户端配置里引用同一个包或端点。

Feishu User MCP 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Feishu User MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Feishu User MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Feishu User MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Windsurf、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Feishu User MCP 能提供哪些能力?

资料显示约 5 个工具;能力标签包括 JavaScript、Claude、协作工具。具体工具清单以官方文档为准。

Feishu User MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Feishu User MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。