MCP-FEISHU
Related Servers
Alternatives to MCP-FEISHU
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA microservice control plane server that integrates with Windsurf IDE by fetching API information from Eolink OpenAPI and exposing it as MCP resources, enabling seamless API integration and management in the development environment.6-
- FlicenseNot gradedqualityBmaintenanceMCP server for Feishu that enables document management, calendar CRUD, and event scheduling via Streamable HTTP transport, deployed on Vercel with OAuth and JWT authentication.-
- 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 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
- AlicenseBqualityDmaintenanceAn MCP server that exposes Feishu (Lark) APIs as standardized tools, enabling knowledge base, document, spreadsheet, and IM operations through any MCP client.3629 npmMIT
- FlicenseNot gradedqualityDmaintenanceA server that enables LLMs to interact with Lark/Feishu services, currently supporting employee information queries via Lark's Contact API.12 npm3-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves a specific defect link, while the other fetches a list of recently updated defects. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is predictable and uniform across the set.
With only 2 tools, the server feels thin for a domain like defect management in Feishu. This minimal set lacks essential operations like creating, updating, or deleting defects, making it under-scoped.
The tool surface is severely incomplete for defect management. It only provides read-only access to defects (link and list), missing critical CRUD operations such as create, update, delete, or search, which will cause agent failures in handling defect workflows.