Back to Skills

mcp-lark

Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.

144stars17forksUpdated 7/14/2026

Security Assessment

Low Risk(80/100)

Detected risks:

Sensitive File Access([SKILL.md] .env)
Security Score80/100

About mcp-lark

mcp-lark connects an agent to Feishu (飞书) / Lark through Lark's official OpenAPI MCP server, letting it manage user information, chats, emails, cloud documents, multidimensional tables (Bitable), tasks, and calendars. It solves the problem of driving the Lark/Feishu suite from natural-language workflows without hand-writing OpenAPI calls, by routing everything through remote MCP endpoints that you register on the Lark MCP Configuration Platform.

The skill is configured through environment variables, prioritizing a workspace `.env` file and falling back to system environment variables, and prompting the user for values when nothing is set. Multiple MCP service URLs and their usage scenarios are declared in a single `LARK_MCP_SERVERS` variable (for example separating chats-and-mails from cloud-documents), so the agent can pick the right endpoint per task. Tool discovery and invocation are done with `mcporter`: listing all tools and their parameters, fetching a specific tool's JSON schema with `jq`, and calling a named tool with typed parameters. For compatibility the skill recommends running commands via `npx -y mcporter` rather than a globally installed binary, and it bundles a reference document describing message-create payloads.

This skill suits teams that already run on Lark/Feishu and want an AI agent to read and act across their collaboration stack — sending messages, working with cloud docs and Bitable, and managing tasks and calendar events. It is most useful once the MCP URL has been obtained from the configuration platform and stored in the environment, after which the agent can enumerate available tools and call them on demand.

FAQ

What Lark/Feishu capabilities does this skill expose?

It can manage user information, chats, emails, cloud documents, multidimensional tables (Bitable), tasks, and calendars, based on the tools exposed by Lark's OpenAPI MCP server.

How do I configure the MCP connection?

Log in to the Lark MCP Configuration Platform, add the MCP services, and obtain the MCP URL. Then set it in environment variables — the skill reads a workspace .env first, then system environment variables, and asks you if nothing is configured. Multiple endpoints and their scenarios are declared in LARK_MCP_SERVERS.

How are individual tools discovered and called?

Use mcporter to list tools and their parameters, and jq to fetch a specific tool's schema. Call a tool with `npx -y mcporter call 'open.larksuite.com/mcp/stream/<token>.<tool_name>' param:"value"`.

Why does the skill use `npx -y mcporter` instead of `mcporter`?

It recommends `npx -y mcporter` to improve compatibility when executing commands, avoiding issues that can arise from a globally installed binary.

All Files

2 files
references/message_create.md24.6 KB
View
SKILL.md1.5 KB
View

Install mcp-lark

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

aahl/skills