Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getlark.ai/llms.txt

Use this file to discover all available pages before exploring further.

Lark exposes a remote MCP server at: 
https://api.getlark.ai/mcp?api_key=<API_KEY>
It provides tools for managing workflows, templates, groups, secret contexts, webhooks, and metrics. It covers the same surface as the CLI.

​
Authentication

Create a Lark API key from Settings > API Keys.

​
Claude (web and desktop)

Claude.ai and the Claude desktop app support remote MCP servers as custom connectors.
  1. Open Customize → Connectors → Add custom connector.
  2. Name it Lark.
  3. Set the Remote MCP URL to https://api.getlark.ai/mcp?api_key=<API_KEY>.
  4. Save.
Open a new chat and ask the agent to list your lark workflows to verify the connection.

​
Cursor

Open Cursor Settings → MCP → Add new MCP server, or edit ~/.cursor/mcp.json directly: 
{
  "mcpServers": {
    "lark": {
      "type": "http",
      "url": "https://api.getlark.ai/mcp",
      "headers": {
        "X-API-Key": "<API_KEY>"
      }
    }
  }
}
Restart Cursor and Lark tools will be available to the agent. Open a new chat and ask the agent to list your lark workflows to verify the connection.

​
Claude Code

We recommend using the claude code plugin instead of the MCP server. See the agents quickstart for more details.
Add Lark as a remote HTTP MCP server: 
claude mcp add --transport http lark https://api.getlark.ai/mcp \
  --header "X-API-Key: <API_KEY>"
Or commit a project-local .mcp.json that reads the key from each user’s environment: 
{
  "mcpServers": {
    "lark": {
      "type": "http",
      "url": "https://api.getlark.ai/mcp",
      "headers": {
        "X-API-Key": "<API_KEY>"
      }
    }
  }
}