lark-agent
Related Servers
Alternatives to lark-agent
No user-submitted related servers found.
Related Servers
- 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 gradedqualityCmaintenanceA zero-configuration MCP server enabling AI assistants to interact with Feishu (Lark) workspace through OAuth authentication, supporting document operations, content creation, and advanced file management.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for TickTick/Dida365 task integration, enabling AI-driven task decomposition and management with automated OAuth authentication.10MIT
- AlicenseNot gradedqualityDmaintenanceOfficial MCP server for Feishu/Lark OpenAPI, enabling AI assistants to interact with Feishu/Lark platform for document processing, messaging, calendar scheduling, and more.7,548 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating TickTick task management with AI applications, enabling task and project operations via natural language.8 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server for operating Feishu Docs, folders, and attachments, and sending notifications via custom bot webhooks. Enables AI assistants to automate document workflows in Feishu.1MIT
TDQS
Scored across 16 tools
Most tools target distinct operations (create, list, comment, transition), but update_task and batch_update_tasks overlap significantly since batch_update_tasks also supports single-item updates. Additionally, update_task exposes a status field that partially overlaps with transition_task_status, and get_tasks' related_to filter overlaps with list_child_tasks.
The dominant verb_noun pattern is consistent throughout, and most names are self-explanatory. Minor deviations exist: list_projects/list_task_comments vs get_tasks/get_task_detail use both 'list' and 'get' for similar listing operations, and create_task vs add_task_comment mix 'create' and 'add'.
At 16 tools, the surface is slightly above the typical 3-15 well-scoped range but still appropriate for the breadth of Feishu project workflows. Each tool serves a plausible need, so the count is not excessive.
The tool set covers the core lifecycle well: project discovery, task create/get/update, comments CRUD, status transition requirements and execution, child-task binding, and field option lookup. The main gap is the absence of a delete_task tool, and there is no direct way to create or manage projects, though that may be out of scope.