A
licenseB
qualityD
maintenanceEnables interaction with Feishu (Lark) via MCP for sending messages, managing calendar events, searching documents, and reading/writing bitable records.
8
Apache 2.0
lark-mcp-server
by YuanZhiTech
Related Servers
Alternatives to lark-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI clients to send, read, reply, and search messages on Feishu/Lark as the user's own identity using MCP tools.725 npmMIT
- -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.9,258 npm-
- AlicenseNot gradedqualityCmaintenanceMCP server for Feishu/Lark API integration, enabling AI agents to send messages, manage groups, create and edit documents and spreadsheets, and search knowledge bases.MIT
- AlicenseNot gradedqualityCmaintenanceIntegrates Feishu/Lark OpenAPI as MCP tools, enabling AI assistants to automate document processing, conversation management, calendar scheduling, and more.9,258 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to access Feishu (Lark) knowledge base and cloud documents through the MCP protocol.21 npm1ISC
TDQS
B3.3/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource and action: sending, replying, listing chats, getting members, viewing messages, sending cards, user info, and agenda. While send_message and send_card both send to a chat, their descriptions clearly distinguish text from interactive cards, leaving no ambiguity.
Naming Consistency5/5
All tool names follow the same pattern: lark_verb_noun (e.g., lark_send_message, lark_list_chats). The verbs are consistent (send, reply, list, get) and all use snake_case, making the naming uniform and predictable.
Tool Count5/5
With 8 tools, the server is well-scoped for a collaboration platform covering messaging, chat management, user info, and agenda reading. Each tool earns its place without being overwhelming or sparse.
Completeness3/5
The server covers core messaging workflows (send, reply, list history) and read operations for chats and users, but lacks write operations for chats (create/update/delete), message editing/deletion, and calendar management beyond reading. These gaps could cause agents to hit dead ends when trying to manage resources.
Maintenance
ActivityStale
ResponsivenessNo issues