feishu-access-bridge
Related Servers
Alternatives to feishu-access-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables reading Feishu documents and Wiki pages, including full content and metadata, via MCP protocol.211 npmISC
- AlicenseAqualityBmaintenanceEnables AI clients to read, write, and search Feishu (Lark) documents, wiki pages, spreadsheets, and bitable records over MCP, with stdio or authenticated HTTP(S) transport.9334 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to access Feishu (Lark) knowledge base and cloud documents through the MCP protocol.11 npm1ISC
- AlicenseBqualityDmaintenanceAn MCP server that exposes Feishu (Lark) APIs as standardized tools, enabling knowledge base, document, spreadsheet, and IM operations through any MCP client.3692 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients such as ChatGPT and Claude to a user's Feishu tenant through OAuth, offering 91 read and write tools covering documents, wiki nodes, spreadsheets, Base records, calendar events, tasks, chats, and cloud files. Per-user authorization, isolated read/write scopes, and token rotation keep actions scoped to the consenting account.334 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP-based service that enables AI models to seamlessly interact with Feishu (Lark) platform, supporting document reading and chatbot messaging capabilities.11 npm53MIT
TDQS
Scored across 2 tools
The two tools serve distinct purposes: one reads Feishu resources, the other checks authentication status. There is no overlap, so an agent can easily distinguish them.
Both tools share the 'feishu_' prefix, but 'read_resource' follows a verb_noun pattern while 'auth_status' is more of a noun phrase. The inconsistency is minor given the small set.
With only two tools, the set is at the lower boundary of acceptable size. It is enough for basic read and status checks but feels thin for a general access bridge.
The set lacks crucial operations like listing available resources, writing/updating, or searching. It covers only reading by URL and auth status, leaving significant gaps for a Feishu integration.