SkillHub ClubShip Full StackFull StackBackendIntegration

mcp-lark

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

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C3.5

Composite score

3.5

Best-practice grade

B84.0

Install command

npx @skill-hub/cli install aahl-skills-mcp-lark

Repository

aahl/skills

Skill path: skills/mcp-lark

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

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack, Backend, Integration.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: aahl.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install mcp-lark into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/aahl/skills before adding mcp-lark to shared team environments
Use mcp-lark for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

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

# MCP Lark / FeiShu
Need to login to the Lark MCP Configuration Platform to add MCP services, obtain the MCP URL, and configure it into environment variables.
- Lark MCP docs: https://open.larksuite.com/document/mcp_open_tools/call-feishu-mcp-server-in-remote-mode
- 飞书 MCP 文档: https://open.feishu.cn/document/mcp_open_tools/end-user-call-remote-mcp-server

## Environment variables
Prioritize fetching from `.env` under the workspace, then use system environment variables. If not configured, ask the user for input and update it to `.env`.
```shell
# Configure multiple MCP service URLs and usage scenarios in environment variables
LARK_MCP_SERVERS='
open.larksuite.com/mcp/stream/xxx:Chats and Mails;
open.larksuite.com/mcp/stream/yyy:Cloud documents;
'
```

## List of available tools
```shell
npx -y mcporter list 'open.larksuite.com/mcp/stream/<token>' --all-parameters

# Get the schema of the specified tool
npx -y mcporter list 'open.larksuite.com/mcp/stream/<token>' --json | jq '.tools[] | select(.name == "<tool_name>")'
```

## Call specified tool
```shell
npx -y mcporter call 'open.larksuite.com/mcp/stream/<token>.<tool_name>' param1:"value1" foo:"bar"
```

## References
- Sent message content: references/message_create.md

## About `mcporter`
To improve compatibility, use `npx -y mcporter` instead of `mcporter` when executing commands.