@dsh-feishu/mcp
Related Servers
Alternatives to @dsh-feishu/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to send and update Feishu/Lark messages, cards, files, and images, read recent chat context and block on human replies, and work with bitables, spreadsheets, and cloud docs through 25 tools. Runs over long connection or HTTP callbacks, so no public IP is needed.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Feishu (Lark) through structured tools for messaging, calendar, tasks, and documents.3MIT

Feishu/Lark OpenAPI MCPofficial
AlicenseNot gradedqualityDmaintenanceA toolkit that enables AI assistants to directly call Feishu/Lark API interfaces for automation scenarios like document processing, conversation management, and calendar scheduling.867MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and write Feishu documents, spreadsheets, messages, and calendars, transfer images and files, and switch between multiple Feishu accounts through a self-hosted remote MCP endpoint.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Feishu/Lark platform APIs for automation scenarios including message management, document operations, calendar scheduling, group management, and Bitable operations through natural language.MIT
- -licenseNot gradedqualityNot gradedmaintenanceA tool designed to help users connect AI Agents with the Feishu/Lark platform, encapsulating Feishu/Lark Open Platform API interfaces as MCP tools for document processing, conversation management, calendar scheduling and more.33,913 npm-
TDQS
Scored across 43 tools
Descriptions explicitly cross-reference siblings with "不适合…请用 X" guidance, so send_text/send_card/send_info_card/send_file/send_image/reply are mostly separable, as are forward vs merge_forward and doc_read vs doc_blocks. Remaining soft spots: send_info_card vs send_card (one is a label/value convenience wrapper over the other), and doc_read vs doc_blocks both read the same document.
Everything is snake_case with a feishu_ prefix, but the verb/noun ordering and verbs themselves are inconsistent: feishu_send_text and feishu_sheet_create put the action first, feishu_bitable_tables and feishu_doc_read are resource-first, and creation is variously create (sheet/doc/chat) vs add (bitable) vs send (message). Several tools drop the action entirely (feishu_forward, feishu_pin, feishu_whoami, feishu_recent, feishu_ask, feishu_recall), and some multiplex actions via parameters (feishu_reaction, feishu_chat_announcement) while others spawn separate tools.
43 tools is large and heavy for a single MCP server; messaging, chat admin, drive, docs, sheets, bitable, wiki and permissions are all packed in. The breadth is real, but an agent picking from 43 similarly-named feishu_* tools pays a real selection cost, and some near-duplicates (send_card vs send_info_card, sheet_meta vs sheet_read) inflate the count.
Coverage is unusually broad: full CRUD on bitable records, sheet read/write/create/meta, doc read/create/append, drive listing, wiki navigation, chat lifecycle, permissions and reactions. Gaps are acknowledged rather than hidden — no block-level doc editing, no adding/removing members from an existing group, and no message search or message edit.