[djiang-jq]

Adds a lark plugin under third_party/ that connects agents to Lark's official hosted MCP server at https://mcp.larksuite.com/mcp, plus its marketplace entry.

This is a URL-only connector in the same shape as the recently added greenhouse and posthog-mcp plugins: mcp.json, manifest, README, CHANGELOG, LICENSE, and logo, with no bundled skills or rules.

Contents

• third_party/lark/mcp.json — single http server pointing at https://mcp.larksuite.com/mcp. No placement field, matching the majority of third-party entries and the two most recent additions.
• third_party/lark/.cursor-plugin/plugin.json — lark / "Lark", integrations category, minClientVersions.cursor of 3.13.0, homepage set to Lark's MCP introduction doc.
• third_party/lark/assets/logo.png — Lark's official bird mark, 256×256 RGBA PNG. The file is byte-identical (sha256 de5fb0fa…) to the avatar published by the larksuite GitHub organization, Lark Technologies Pte. Ltd., so provenance is verifiable rather than a redraw.
• README and CHANGELOG covering install, auth, region scope, and capability categories.
• .cursor-plugin/marketplace.json — appended entry, consistent with how the last several plugins landed.

Scope and verification

node scripts/validate-plugins.mjs passes against both schemas (the same command CI runs).

Two things reviewers should know:

• Egress from the authoring environment blocks mcp.larksuite.com and open.larksuite.com, so the live endpoint and its advertised tool list could not be probed here. The README therefore describes capabilities by category and defers to the hosted runtime and Lark's docs for exact tool names, rather than pinning a tool list that cannot be checked. Worth confirming the connect flow from a client with network access before this is marked approved.
• Only Lark Suite (the international product) is included. China-region Feishu runs a separate server at https://mcp.feishu.cn/mcp; the README and CHANGELOG say so explicitly, and a feishu plugin can follow as its own change.

The root README.md plugin table is intentionally untouched: it already omits the eight most recently added plugins, and neither greenhouse nor posthog-mcp updated it. Re-syncing that table is better as a separate pass than as a one-row edit here.