Lark Needs an Official Remote MCP, Not Just a CLI

Lark should rethink its AI integration strategy. PC first AI integration strategy today is already a questionable assumption.

More and more AI usage is moving to mobile and cloud based assistants, yet Lark chose to build an integration that essentially requires a computer, a local environment, and a CLI. If the goal is to make Lark accessible to AI assistants, why require the user to keep a computer involved at all?

What users actually need is an official Remote MCP server that allows AI assistants to directly connect to Lark, turning Lark Docs, Messages, Calendar, Base, and other capabilities into a truly personal, always available work assistant.

Not a CLI that requires users to install and configure tools on a specific computer, then rely on an agent or terminal to interact with Lark.

A CLI is useful for developers and coding agents. It is not the right interface for bringing Lark into the broader AI assistant ecosystem.

If Lark wants to become an AI native work platform, it should make Lark directly accessible to AI assistants, rather than requiring users to learn how to connect a CLI to an agent.

Please prioritize an official, secure, OAuth-based Remote MCP endpoint. That would dramatically lower the barrier for AI apps to integrate with Lark and make Lark genuinely useful as a personal AI work assistant.

The issue names no files, tests, or entry points; begin by reviewing the existing CLI integration surface and how Lark capabilities are exposed. Before implementation, clarify the Remote MCP endpoint, OAuth flow, supported capabilities, security requirements, and acceptance criteria with maintainers.