npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@danyow/lark-mcp

v0.5.6

Published

Feishu/Lark OpenAPI MCP

Readme

Feishu/Lark OpenAPI MCP

npm version npm downloads Node.js Version

English | 中文

Developer Documentation Retrieval MCP

Official Document

Trouble Shooting

⚠️ Beta Version Notice: This tool is currently in Beta stage. Features and APIs may change, so please stay updated with version releases.

This is the Feishu/Lark official OpenAPI MCP (Model Context Protocol) tool designed to help users quickly connect to the Feishu/Lark platform and enable efficient collaboration between AI Agents and Feishu/Lark. The tool encapsulates Feishu/Lark Open Platform API interfaces as MCP tools, allowing AI assistants to directly call these interfaces and implement various automation scenarios such as document processing, conversation management, calendar scheduling, and more.

Preparation

Creating a Feishu/Lark Application

Before using the lark-mcp tool, you need to create a Feishu/Lark application:

  1. Visit the Feishu Open Platform or Lark Open Platform and log in
  2. Click "Console" and create a new application
  3. Obtain the App ID and App Secret, which will be used for API authentication
  4. Add the necessary permissions for your application based on your usage scenario
  5. If you need to call APIs as a user, set the OAuth 2.0 redirect URL to http://localhost:3000/callback

For detailed application creation and configuration guidelines, please refer to the Feishu Open Platform Documentation - Creating an Application.

Installing Node.js

Before using the lark-mcp tool, you need to install the Node.js environment.

Using the Official Installer (Recommended):

  1. Visit the Node.js website
  2. Download and install the LTS version
  3. After installation, verify in the terminal:
node -v
npm -v

Quick Start

Using with Trae/Cursor/Claude

To integrate Feishu/Lark functionality in AI tools like Trae, Cursor or Claude, install using the button below.

Install MCP Server

Install MCP Server Install MCP Server

or add the following to your configuration file:

{
  "mcpServers": {
    "lark-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@larksuiteoapi/lark-mcp",
        "mcp",
        "-a",
        "<your_app_id>",
        "-s",
        "<your_app_secret>"
      ]
    }
  }
}

If you need to access APIs with user identity, you need to login first using the login command in the terminal. Note that you need to configure the application's redirect URL in the developer console first, default is http://localhost:3000/callback


# Login and get user access token
npx -y @larksuiteoapi/lark-mcp login -a cli_xxxx -s yyyyy
   
# Or optionally, login with specific OAuth scope - if not specified, all permissions will be authorized by default
npx -y @larksuiteoapi/lark-mcp login -a cli_xxxx -s yyyyy --scope offline_access docx:document

Then add the following to your configuration file:

{
  "mcpServers": {
    "lark-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@larksuiteoapi/lark-mcp",
        "mcp",
        "-a",
        "<your_app_id>",
        "-s",
        "<your_app_secret>",
        "--oauth",
        "--token-mode", "user_access_token"
      ]
    }
  }
}

Note: When enabling --oauth, it's recommended to explicitly set --token-mode to user_access_token, which means calling APIs with user access tokens, suitable for accessing user resources or scenarios requiring user authorization (such as reading personal documents, sending IM messages). If you keep the default auto, some APIs AI may fallback to tenant_access_token, which could result in insufficient permissions or inability to access user private data.

Domain Configuration

Based on your usage scenario, lark-mcp supports configuring different domain environments:

Feishu (China Version):

  • Default uses https://open.feishu.cn domain
  • Suitable for users in China

Lark (International Version):

  • Uses https://open.larksuite.com domain
  • Suitable for overseas users or international version of Lark

To switch to the international version of Lark, add the --domain parameter in your configuration:

{
  "mcpServers": {
    "lark-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@larksuiteoapi/lark-mcp",
        "mcp",
        "-a",
        "<your_app_id>",
        "-s",
        "<your_app_secret>",
        "--domain",
        "https://open.larksuite.com"
      ]
    }
  }
}

💡 Tip: Ensure your application is created in the corresponding domain environment's open platform. International version applications cannot be used with Feishu China version, and vice versa.

Custom API Configuration

⚠️ File Upload/Download: File upload and download operations are not yet supported

⚠️ Document Editing: Direct editing of Feishu cloud documents is not supported (only importing and reading are available)

By default, the MCP service enables common APIs. To enable other tools or only specific APIs or presets, you can specify them using the -t parameter in the MCP Client configuration (JSON):

{
  "mcpServers": {
    "lark-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@larksuiteoapi/lark-mcp",
        "mcp",
        "-a", "<your_app_id>",
        "-s", "<your_app_secret>",
        "-t", "im.v1.message.create,im.v1.message.list,im.v1.chat.create,preset.calendar.default"
      ]
    }
  }
}

For detailed information about all preset tool collections and which tools are included in each preset, please refer to the Preset Tool Collections Reference.

A complete list of all supported Feishu/Lark tools can be found in tools.md.

⚠️ Notice:Non-preset APIs have not undergone compatibility testing, and the AI may not perform optimally during the process of understanding and using them.

Development Integration

Developers can refer to the minimal example for integrating with Agent: lark-samples/mcp_quick_demo.

You can also refer to the Lark bot integration example: lark-samples/mcp_larkbot_demo/nodejs.

This example demonstrates how to integrate MCP capabilities into Feishu/Lark bots, triggering tool calls and message sending through bot conversations, suitable for scenarios that integrate existing tools into Bot.

Advanced Configuration

For detailed configuration options and deployment scenarios, please refer to our Configuration Guide.

For detailed information about all available command line parameters and their usage, please refer to the Command Line Reference.

FAQ

Related Links

Feedback

Issues are welcome to help improve this tool. If you have any questions or suggestions, please raise them in the GitHub repository.