Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Feishu (Lark) OpenAPI MCP Server send a message to the dev group chat saying the release is live"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Connect DeepSeek Harness (DSH) to Feishu / Lark through the official @larksuiteoapi/lark-mcp server: the plugin spawns the official MCP server as a subprocess with your Feishu app credentials, discovers its tools, and registers them on the agent as mcp__feishu__* — so the DSH agent can send IM messages, read/write Bitable (multidimensional tables), manage docs, calendar, drive, and more, using your Feishu app's permissions.
A web settings panel (Settings → 飞书) configures the App ID / App Secret, shows connection status, and lists the discovered tools.
中文说明见 README.zh.md。
Official MCP server: drives @larksuiteoapi/lark-mcp (Feishu OpenAPI MCP, Beta) over stdio — no reverse proxy, no public IP needed.
Full tool surface: every tool the official server exposes (per your app's permissions and -t presets) becomes an agent tool mcp__feishu__* — e.g. mcp__feishu__im_v1_message_create, mcp__feishu__bitable_v1_app_create.
App identity or user identity: configure appId/appSecret (tenant identity) and optionally a userAccessToken (user identity for private resources).
Agent tools: feishu_status / feishu_config / feishu_test / feishu_tools.
Web settings panel: configure credentials, test the connection, and see the live tool list.
Related MCP server: Feishu/Lark OpenAPI MCP
Requires DeepSeek Harness ≥ 0.1.5-rc.1 (declared as dsh.engines.dsh in the package manifest, so the DSH plugin marketplace can report it) and is verified against 0.1.5-rc.1. This build carries the DSH 0.1.5 adaptations: the strict tool-result contract (lossless-JSON snapshot, additionalProperties: false schema validation, and output.render returning ContentBlock[]) plus executable resolution that survives a launchd-started host whose PATH is only /usr/bin:/bin. Since this version the peerDependencies range explicitly declares compatibility with DSH 0.2.0-rc.2 (^0.2.0-rc.2 is now included), so no compatibility warning appears on 0.2.0-rc.2. No functional change.
A Feishu self-built app: Feishu Open Platform → Developer Console → create an app.
Add the permissions you need (im:message, bitable:app, docx:document, calendar:calendar, drive:drive …) and publish a version.
Install the plugin and configure the App ID / App Secret.
# from npm (published package)
dsh plugin --profile web add dsh-feishu-mcp
# or local development
dsh plugin --profile web add link:/path/to/dsh-feishu-mcp
# restart dsh web to activateVia the web settings panel (Settings → 飞书), or the agent tool:
feishu_config appId=<cli_xxx> appSecret=<your_secret>Optional user identity (for private resources):
feishu_config userAccessToken=<user_access_token>After connecting, the agent sees the Feishu tools as mcp__feishu__*. Verify:
feishu_testpnpm install
pnpm build && node tests/smoke.mjsMIT
This server cannot be deployed
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
