Lark Mcp Server

Created By
larksuitea year ago
Overview

What is Lark MCP Server?

Lark MCP Server is a tool designed to facilitate integration with the Feishu/Lark platform, enabling efficient collaboration between AI agents and the platform through its OpenAPI Model Context Protocol (MCP).

How to use Lark MCP Server?

To use Lark MCP, create a Feishu/Lark application to obtain your App ID and App Secret, install Node.js, and then install the Lark MCP tool globally using npm. You can then configure and run the tool using command line parameters or a configuration file.

Key features of Lark MCP Server?

  • Complete toolkit for Feishu/Lark API interfaces, including document processing and conversation management.
  • Dual authentication support for App Access Token and User Access Token.
  • Flexible communication protocols, supporting both standard input/output and Server-Sent Events (SSE) modes.

Use cases of Lark MCP Server?

  1. Automating document processing tasks.
  2. Managing conversations and group chats programmatically.
  3. Scheduling calendar events through API calls.

FAQ from Lark MCP Server?

  • How do I connect to the Feishu/Lark API?
    Ensure your APP_ID and APP_SECRET are correct and that you have the necessary permissions.

  • What should I do if my user access token expires?
    Implement an automatic token refresh mechanism or use app_access_token instead.

  • Can I use Lark MCP for file uploads?
    Currently, file upload functionality is not supported but will be in future versions.

Server Config

{
  "mcpServers": {
    "lark-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@larksuiteoapi/lark-mcp",
        "mcp",
        "-a",
        "<your_app_id>",
        "-s",
        "<your_app_secret>",
        "-u",
        "<your_user_token>"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
larksuite
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago