feishu-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEISHU_APP_ID | Yes | Your Feishu App ID | |
| FEISHU_APP_SECRET | Yes | Your Feishu App Secret |
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 |
|---|---|
| read_feishu_documentA | 读取飞书文档的内容。根据文档 ID 或完整 URL 获取文档的标题和完整文本内容。支持普通文档和知识库(Wiki)文档。 |
| get_feishu_document_metaA | 获取飞书文档的元信息（标题）。根据文档 ID 或完整 URL 获取文档标题，不返回文档内容。支持普通文档和知识库(Wiki)文档。 |
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 2 tools
read_feishu_document returns full content, while get_feishu_document_meta returns only metadata. Their purposes are clear and non-overlapping, so agents can easily select the right tool.
Both tools follow a consistent [verb]_feishu_document pattern, with read and get as action prefixes. The naming is uniform and predictable.
At 2 tools, the server feels thin for a document-focused MCP. While the current tools are focused, the small set suggests limited scope.
The server covers reading content and metadata but lacks listing, searching, creating, updating, or deleting documents. This is a significant gap for a Feishu document server, limiting agents to only read operations.