Lark MCP Server

What is Lark MCP Server?

Lark MCP Server is a Model Context Protocol (MCP) server implementation for Lark/Feishu. It bridges AI models with Lark’s collaboration platform, enabling MCP‑compatible applications to send messages, manage calendar events, and interact with Lark services.

How to use Lark MCP Server?

Clone the repository, install dependencies (npm install), and build (npm run build). Then configure an MCP client—such as Claude Desktop—by adding the server to its claude_desktop_config.json with the required environment variables (LARK_APP_ID, LARK_APP_SECRET, LARK_USER_ID, LARK_CALENDAR_ID, LARK_USER_ACCESS_TOKEN). Restart the client to connect.

Key features of Lark MCP Server

• Send direct messages to Lark users
• List calendar events within a specified time range
• Create new calendar events with custom details
• Add attendees (users, groups, meeting rooms, external emails) to events

Use cases of Lark MCP Server

• An AI assistant sends a notification to a Lark user
• An AI agent checks your calendar for upcoming events
• A scheduling bot creates a meeting and adds participants
• Automated event creation from natural language requests

FAQ from Lark MCP Server

What are the prerequisites for running the server?

Node.js v18 or higher, a registered Lark/Feishu application with appropriate permissions, and a user access token for calendar operations.

How does the server communicate with MCP clients?

It uses the standard I/O (stdio) transport layer. MCP clients launch the server as a child process and communicate through its stdin and stdout channels.

How do I set up the server with Claude Desktop?

Add the server configuration to claude_desktop_config.json, providing the correct path to the built index.js and the required environment variables. Then restart Claude Desktop completely.

What are common issues and how do I troubleshoot them?

Check server logs (written to stderr). Common causes include missing environment variables, expired access tokens, insufficient Lark application permissions, or invalid request parameters.

What authentication does the server use?

Authentication is handled via environment variables: Lark app credentials (LARK_APP_ID, LARK_APP_SECRET) and a user access token (LARK_USER_ACCESS_TOKEN).