t1k:comms-mcp:lark
| Field | Value |
|---|---|
| Module | lark |
| Version | 0.5.3 |
| Effort | medium |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:comms-mcp:larkLark / Feishu (comms-mcp)
Section titled “Lark / Feishu (comms-mcp)”Send/read IM messages, manage chats, and read Base/Docs/Contact data through an MCP server.
Source
Section titled “Source”Wraps The1Studio/lark-openapi-mcp (fork of larksuite/lark-openapi-mcp, MIT, pinned v0.5.1). Chosen as the official ByteDance Feishu/Lark OpenAPI MCP (~0.9k★ upstream) — best long-term support and the broadest tool surface. Run from the fork clone (npm @larksuiteoapi/lark-mcp exists but we use the fork for control).
When to Use
Section titled “When to Use”- Posting notifications/alerts to a Feishu/Lark chat from an agent
- Reading chat history, listing/searching chats and members
- Reading Base (Bitable) records, Docs (docx), or Contact data
- Wiring Feishu/Lark into a comms workflow
Run ~/.claude/skills/t1k-comms-mcp-setup/scripts/install-lark.sh (for a project-scoped install it’s .claude/skills/t1k-comms-mcp-setup/scripts/install-lark.sh) — clones + bun run build the fork, then registers the MCP server if APP_ID+APP_SECRET are set, else prints the command.
App prerequisites (Feishu open.feishu.cn or Lark open.larksuite.com developer console):
- Create a custom app → copy App ID (
APP_ID) + App Secret (APP_SECRET). - Add API scopes for the tools you need (e.g.
im:message,docx:document,bitable). - App region is fixed — a Feishu app does not work against Lark international and vice versa.
Register (user scope, after build):
claude mcp add lark --scope user -- node /ABS/PATH/lark-openapi-mcp/dist/cli.js mcp -a "$APP_ID" -s "$APP_SECRET" --mode stdioLark international — append --domain https://open.larksuite.com (default domain is Feishu/China open.feishu.cn).
Prereqs: Node ≥20, yarn, built dist/cli.js, a Feishu/Lark custom app with scopes. On Linux the native keytar dep needs libsecret (libsecret-1-0 / libsecret-devel) — headless/CI builds may fail it.
MCP Tools
Section titled “MCP Tools”Tools are preset-based via -t/--tools (default preset.default = IM + Base + Doc + Contact). Tool IDs are {domain}.{version}.{resource}.{action}.
| Tool | Purpose |
|---|---|
im.v1.message.create | Send a message to a chat/user |
im.v1.message.list | Read recent messages in a chat |
im.v1.chat.create | Create a chat |
im.v1.chat.list / im.v1.chat.search | List / search chats |
im.v1.chatMembers.get | List members of a chat |
Other presets: preset.light, preset.im.default, preset.base.default, preset.base.batch, preset.doc.default, preset.task.default, preset.calendar.default. 61 API domains exist (im/bitable/docx/drive/sheets/wiki/calendar/contact/task/approval/vc/mail/…) but non-preset tools are untested for AI use and flood the tool list — stay on presets.