Feishu MCP Server

Most developer tooling work still happens through a UI a human drives. Feishu MCP server moves it into the conversation instead. MCP server provides Feishu related operations to AI encoding agents such as cursor 飞书MCP插件，读取文档、发送消息、合同审批、数据处理.....

The short version

MCP server provides Feishu related operations to AI encoding agents such as cursor 飞书MCP插件，读取文档、发送消息、合同审批、数据处理.....

The tools it exposes

The server publishes 1 tool. What each one is for:

• get_feishu_doc — The get_feishu_doc tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: FEISHU_APP_ID, FEISHU_APP_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

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. Feishu's toolset — get_feishu_doc — is a fair guide to whether it matches your workflow. It is maintained by Li-vien; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Feishu's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.