Lark_doc

Created By
Xeonicea year ago
Overview

What is MCP Lark Doc Manage?

MCP Lark Doc Manage is a Model Context Protocol server designed for searching and accessing Lark (Feishu) documents, enabling users to retrieve and manage document content efficiently.

How to use MCP Lark Doc Manage?

To use MCP Lark Doc Manage, you need to create a Lark Enterprise Application, configure the necessary environment variables, and run the server using the provided command. Ensure you have the required permissions set up in your Lark application.

Key features of MCP Lark Doc Manage?

  • Supports access to both Lark Doc and Wiki document types.
  • Automatic document type detection and ID extraction.
  • OAuth-based user authentication with token management.
  • Comprehensive error handling and reporting.

Use cases of MCP Lark Doc Manage?

  1. Retrieving content from Lark documents for analysis.
  2. Searching for specific information within Lark Wiki documents.
  3. Managing document access and permissions in a collaborative environment.

FAQ from MCP Lark Doc Manage?

  • What types of documents can I access?

You can access both Lark Docs and Wiki documents.

  • Do I need to set up an application to use this?

Yes, you must create a Lark Enterprise Application and configure it before using the server.

  • What happens if I encounter an error?

The server provides detailed error messages to help troubleshoot issues.

Server Config

{
  "mcpServers": {
    "lark_doc": {
      "command": "/path/to/your/uvx",
      "args": [
        "mcp-lark-doc-manage"
      ],
      "env": {
        "LARK_APP_ID": "your_app_id",
        "LARK_APP_SECRET": "your_app_secret",
        "OAUTH_HOST": "localhost",
        "OAUTH_PORT": "9997",
        "FOLDER_TOKEN": "your_folder_token",
        "DEBUG": "1"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Xeonice
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)

a day ago
Crevio

2 days ago