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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago