Lark MCP KAIpany MCP Server

Feishu/Lark OpenAPI MCP

Local serverstdio

What is the Lark MCP KAIpany MCP server?

Lark mcp kaipany mcp server lets Claude, Cursor and other MCP clients work with Lark MCP KAIpany directly. Feishu/Lark OpenAPI MCP.

What Lark MCP KAIpany does

Developer Documentation Retrieval MCP | Official Document

Key capabilities

  • 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
  • Supports Server-Sent Events (SSE) mode, providing HTTP-based interfaces
  • Supports multiple configuration methods, adapting to different usage scenarios

Installing the lark mcp kaipany mcp server

The server is distributed via npm as @larksuiteoapi/lark-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 2 environment variables: APP_ID, APP_SECRET. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Lark MCP KAIpany sits in that group. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by KAIpany.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the lark mcp kaipany mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

How to install the Lark MCP KAIpany MCP server

{
  "mcpServers": {
    "lark-mcp-kaipany": {
      "command": "npx",
      "args": ["-y", "@larksuiteoapi/lark-mcp"],
      "env": {
        "APP_ID": "your-value",
        "APP_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
APP_IDConfiguration value read at startup.Optional
APP_SECRETCredential the server authenticates with.Yes

Frequently asked questions

It connects Lark MCP KAIpany to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Lark MCP KAIpany directly.