MCP KAIpany MCP Server

Feishu/Lark OpenAPI MCP. The mcp kaipany mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

This is the Feishu/Lark official OpenAPI MCP (Model Context Protocol) tool designed to help users quickly connect to the Feishu/Lark platform and enable efficient collaboration between AI Agents and Feishu/Lark. The tool encapsulates Feishu/Lark Open Platform API interfaces as MCP tools, allowing AI assistants to directly call these interfaces and implement various automation scenarios such as document processing, conversation management, calendar scheduling, and more.

• Complete Feishu/Lark API Toolkit: — Encapsulates almost all Feishu/Lark API interfaces, including message management, group management, document operations, calendar events, Bitable, and other core functional areas
• Dual Authentication Support: —
• Supports App Access Token authentication
• Supports User Access Token authentication
• Flexible Communication Protocols: —
• Supports standard input/output stream (stdio) mode, suitable for integration with AI tools like Trae/Cursor/Claude

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @larksuiteoapi/lark-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 2 environment variables: APP_ID, APP_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by kaipanytool3; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp kaipany mcp server does with a few real requests.