feishu_mcp_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBHOOK | Yes | The webhook URL for the Feishu robot |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageA | |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear: it sends a Feishu message.
The single tool follows a clear verb_noun pattern (send_message), which is consistent with standard naming conventions. There are no other tools to introduce inconsistency.
A Feishu MCP server with only a send_message tool is extremely limited. Feishu offers a wide range of APIs, and one tool is far too few for the apparent scope of a server dedicated to the platform.
The server only supports sending messages, lacking essential operations like reading messages, listing chats, searching, or managing contacts. This is a severely incomplete surface for a Feishu integration.