My Lark Doc MCP Server

# MCP Server My Lark Doc A Model Context Protocol server for searching and accessing Lark(Feishu) documents. ## Features ### Document Content Access

Local serverstdio

What is the My Lark Doc MCP server?

MCP Server My Lark Doc A Model Context Protocol server for searching and accessing Lark(Feishu) documents. ## Features ### Document Content Access - Supports both Lark Doc and Wiki document types - Automatically handles document type. That is what the my lark doc mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 9 tools. What each one is for:

  • Purpose — Retrieve document content from Lark
  • Args — documentUrl (string) - The URL of the Lark document
  • Returns — Document content in text format
  • Supports — - Doc URLs: https://xxx.feishu.cn/docx/xxxxx
  • title — Document title
  • url — Document URL
  • create_time — Document creation time
  • update_time — Document last update time
  • Authentication — The Authentication tool exposed by this server

What it needs from you

Configuration is passed through the environment: LARK_APP_ID, LARK_APP_SECRET, OAUTH_HOST, OAUTH_PORT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

mcp-server-my-lark-doc on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. My Lark Doc's toolset — Purpose, Args, Returns and 6 more — is a fair guide to whether it matches your workflow. It is maintained by T0UGH; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch My Lark Doc.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
PurposeRetrieve document content from Lark
ArgsdocumentUrl (string) - The URL of the Lark document
ReturnsDocument content in text format
Supports- Doc URLs: https://xxx.feishu.cn/docx/xxxxx
titleDocument title
urlDocument URL
create_timeDocument creation time
update_timeDocument last update time
AuthenticationThe Authentication tool exposed by this server.

How to install the My Lark Doc MCP server

{
  "mcpServers": {
    "server-my-lark-doc": {
      "command": "uvx",
      "args": ["mcp-server-my-lark-doc"],
      "env": {
        "LARK_APP_ID": "your-value",
        "LARK_APP_SECRET": "your-value",
        "OAUTH_HOST": "your-value",
        "OAUTH_PORT": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LARK_APP_IDConfiguration value read at startup.Optional
LARK_APP_SECRETCredential the server authenticates with.Yes
OAUTH_HOSTEndpoint or connection string the server talks to.Optional
OAUTH_PORTConfiguration value read at startup.Optional

Example prompts to try

  • Use My Lark Doc to Purpose.
  • Use My Lark Doc to Args.
  • Use My Lark Doc to Returns.

Frequently asked questions

Your Lark app must have the following permissions: `wiki:wiki:readonly`, `wiki:node:read`, `docx:document:readonly`, and `search:docs:read`.