larksuite-connector-mcp
Facilitates integration between AI agents and the Feishu/Lark ecosystem APIs. Enables automation for document manipulation, dialogue handling, and scheduling functions. Incorporates support for multiple authentication schemes and varied communication protocols for seamless linkage.
Author

larksuite
Quick Info
Actions
Tags
Feishu/Lark API Integration Module (MCP)
English | 中文
Knowledge Retrieval MCP Documentation
❗ Experimental Release Warning: This utility package is presently undergoing Beta testing. API specifications and feature sets are subject to revision; maintain awareness of subsequent package updates.
This official Model Context Protocol (MCP) package for the Feishu/Lark Open Platform is engineered to swiftly bridge AI systems with the Feishu/Lark infrastructure, fostering enhanced operational efficiency between intelligent assistants and the platform. The package abstracts the raw Feishu/Lark Open Platform interfaces into consumable MCP tools. This abstraction layer allows AI assistants to directly invoke these interfaces, realizing diverse automation workflows such as content processing, interaction management, and time slot reservation.
Prerequisites for Setup
Establishing a Feishu/Lark Application
Utilization of the larksuite-connector-mcp requires the prior creation of a dedicated Feishu/Lark application:
- Navigate to the Feishu Open Platform or Lark Open Platform and authenticate.
- Access the "Console" and initiate the creation of a novel application instance.
- Securely record the generated Application Identifier (App ID) and Application Key (App Secret); these credentials are vital for API authentication.
- Grant the application the requisite operational permissions dictated by your planned use cases.
- If API calls necessitating user context are anticipated, configure the OAuth 2.0 callback endpoint to
http://localhost:3000/callback.
For comprehensive instructions on application genesis and configuration, consult the Feishu Open Platform Documentation - Application Creation Guide.
Node.js Environment Requirement
Installation of the Node.js runtime is mandatory before deploying the larksuite-connector-mcp utility.
Recommended Installation Method (Official Installer):
- Browse the Node.js official site.
- Download and install the Long-Term Support (LTS) distribution.
- Validate the installation via the command line interface:
bash node -v pm -v
Rapid Initiation Guide
Integration with AI Environments (e.g., Trae/Cursor/Claude)
To embed Feishu/Lark capabilities within supported AI environments like Trae, Cursor, or Claude, employ the provided installation mechanism.
or manually append the following configuration block to your primary configuration manifest:
{
"mcpServers": {
"lark-mcp": {
"command": "npx",
"args": [
"-y",
"@larksuiteoapi/lark-mcp",
"mcp",
"-a",
"
To utilize APIs requiring end-user authorization, an initial authentication via the command line is necessary. Remember to pre-configure the application's redirect URI in the developer portal (default is http://localhost:3000/callback).
bash
Authenticate and obtain user access token
npx -y @larksuiteoapi/lark-mcp login -a cli_xxxx -s yyyyy
Optional: Specify granular OAuth scopes during login (defaults to all authorized scopes)
npx -y @larksuiteoapi/lark-mcp login -a cli_xxxx -s yyyyy --scope offline_access docx:document
Subsequently, update your configuration file with these parameters:
{
"mcpServers": {
"lark-mcp": {
"command": "npx",
"args": [
"-y",
"@larksuiteoapi/lark-mcp",
"mcp",
"-a",
"
Note on OAuth: When --oauth is activated, setting --token-mode explicitly to user_access_token is advisable. This ensures API interactions are performed using tokens scoped to the individual user, essential for accessing personal data (e.g., reading private documents, sending direct messages). If the default auto mode is retained, certain calls might default to tenant_access_token, potentially leading to authorization failures when accessing user-specific resources.
Environment Endpoint Configuration
lark-mcp supports environment switching based on your operational locale:
Feishu (Mainland China Deployment):
- Utilizes https://open.feishu.cn as the default endpoint.
- Appropriate for deployments targeting mainland Chinese infrastructure.
Lark (Global Deployment):
- Employs https://open.larksuite.com as the endpoint.
- Suitable for international user bases or the global Lark instance.
To utilize the international Lark endpoint, incorporate the --domain flag in your configuration setup:
{
"mcpServers": {
"lark-mcp": {
"command": "npx",
"args": [
"-y",
"@larksuiteoapi/lark-mcp",
"mcp",
"-a",
"
❗ Crucial Tip: Application registration must correspond to the selected endpoint domain. An application registered for the China Feishu ecosystem cannot interface correctly with the international Lark service, and vice versa.
Tailored API Selection
⚠️ Unsupported Operations: Binary file transfer (upload/download) functionality is presently unavailable.
⚠️ Document Interaction Limitation: Direct manipulation (editing) of Feishu native documents is not supported; read and import functionalities are functional.
The MCP service activates a standard set of commonly used APIs by default. To enable specific tools, limit the exposed interfaces, or utilize predefined bundles, specify them via the -t argument within the MCP Client's configuration object (JSON):
{
"mcpServers": {
"lark-mcp": {
"command": "npx",
"args": [
"-y",
"@larksuiteoapi/lark-mcp",
"mcp",
"-a", "
For a comprehensive catalog of available API bundles and their constituent tools, consult Preset Tool Catalog.
The exhaustive inventory of all supported Feishu/Lark interfaces is documented in tools.md.
❗ Compatibility Note: Unlisted (non-preset) APIs have not undergone rigorous compatibility validation. AI model performance might be suboptimal when attempting to interpret and invoke these interfaces.
Development Integration Examples
Developers seeking guidance on integrating this utility with an Agent can review the minimal demonstration located at: lark-samples/mcp_quick_demo.
Alternatively, examine the Lark Bot integration pattern in Node.js: lark-samples/mcp_larkbot_demo/nodejs.
This latter example illustrates embedding MCP functionality within Feishu/Lark bots, enabling tool invocation and message transmission directly through bot interactions—ideal for extending existing bot functionalities with platform capabilities.
Advanced Operational Parameters
For an in-depth exploration of comprehensive configuration options and deployment strategies, please navigate to our Configuration Manual.
Details regarding all accessible command-line flags and their proper syntax are provided in the CLI Parameter Reference.
Frequently Asked Queries (FAQ)
- Troubleshooting and FAQs
- Common Problems and Practical Use Cases
Relevant Online Resources
- Feishu Open Platform Portal
- Development Guide: OpenAPI MCP
- Lark Global Open Platform
- Feishu Open Platform API Documentation Hub
- Node.js Official Software Site
- npm Registry Documentation
Contribution and Feedback
We welcome bug reports and suggestions to foster continuous enhancement of this package. Please submit any inquiries or recommendations via an issue ticket on the GitHub repository.
WIKIPEDIA: Business management tools encompass the entire spectrum of systems, software applications, governance frameworks, computational methodologies, and strategic approaches utilized by enterprises to effectively navigate dynamic market conditions, secure a sustainable competitive advantage, and systematically elevate organizational performance metrics.== Overview == Management utilities are segmentable according to specific organizational divisions and functional requirements, such as strategic foresight instruments, workflow governance mechanisms, data retention systems, personnel resource management applications, analytical decision support tools, performance monitoring frameworks, and so forth. A functional categorization commonly addresses these core organizational pillars:
Mechanisms employed for data ingestion and integrity verification across all departments. Software designed for monitoring and optimizing operational workflows. Systems dedicated to data aggregation and facilitating informed decision-making. Contemporary business tooling has undergone rapid transformation in the last decade, driven by accelerated technological advancement, making the selection of optimal solutions for any corporate context increasingly complex. This difficulty stems from persistent pressures to reduce expenditures while simultaneously maximizing revenue, the imperative to deeply comprehend client requirements, and the challenge of reliably delivering products conforming precisely to those needs. In this environment, executives must adopt a strategic posture toward management technologies, resisting the urge to adopt the newest trend without proper vetting. Over-reliance on unmodified external tools often precipitates system instability. Consequently, business management solutions must be chosen with discernment and then rigorously tailored to the organization’s unique operational profile, rather than the reverse.
== Predominant Selections == Data from a 2013 Bain & Company survey highlighted global adoption patterns for business utilities, reflecting regional demands shaped by prevailing economic climates. The ten most frequently cited tools included:
Strategic planning frameworks Client relationship management systems (CRM) Employee satisfaction assessment protocols Competitive benchmarking processes Balanced scorecard implementation Core competency identification Outsourcing strategies Organizational change management programs Supply chain optimization Mission and vision articulation Market segmentation analysis Total Quality Management (TQM)
== Enterprise Software Applications == Software solutions, or collections of interconnected computer programs, utilized by organizational personnel to execute various business mandates are defined as business software (or business applications). These applications are instrumental in augmenting productivity levels, quantifying performance outcomes, and executing diverse corporate functions with high precision. The field progressed from initial Management Information Systems (MIS) to expansive Enterprise Resource Planning (ERP) architectures. Subsequently, Customer Relationship Management (CRM) functionalities were integrated, leading ultimately to the current paradigm of cloud-based enterprise management suites. While a verifiable link exists between IT investments and organizational success, two factors are paramount for realizing substantive value: the efficacy of the deployment process and the judicious selection and customization of the requisite tools.
== Tools Tailored for Small and Medium Enterprises (SMEs) == Specialized toolsets for SMEs are crucial as they furnish scalable methods for resource optimization...
