Can I use Lark Suite as a CLI?

Yes. KosmoKrator exposes a Lark Suite CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Lark Suite through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Lark Suite tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Lark Suite credentials stored?

Lark Suite credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Lark Suite MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

communication

Lark Suite CLI for Headless Automation

Use the Lark Suite CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write Bearer token auth

Submit Lark Suite feedback View package source

Lark Suite CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Lark Suite CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Lark Suite CLI for Headless Automation
kosmokrator integrations:configure lark --set access_token="$LARK_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call lark.lark_list_chats '{"page_size":1,"page_token":"example_page_token"}' --json

Discovery Before Execution

Agents and scripts can inspect Lark Suite docs and schemas before choosing a function.

kosmo integrations:docs lark --json
kosmo integrations:docs lark.lark_list_chats --json
kosmo integrations:schema lark.lark_list_chats --json
kosmo integrations:search "Lark Suite" --json
kosmo integrations:list --json

Useful Lark Suite CLI Functions

Function	Type	Parameters	Description
`lark.lark_list_chats`	Read	page_size, page_token	List chats the current authenticated user belongs to in Lark. Returns chat IDs, names, and metadata for use with other Lark tools.
`lark.lark_get_chat`	Read	chat_id	Get detailed information about a specific Lark chat, including its name, description, owner, and member count.
`lark.lark_create_chat`	Write	chat_id, name	Create a new group chat in Lark. Specify a chat ID and name for the new chat.
`lark.lark_list_messages`	Read	chat_id, page_size, page_token	List messages in a specific Lark chat. Returns message IDs, sender info, content, and timestamps.
`lark.lark_send_message`	Write	chat_id, content, msg_type	Send a message to a specific Lark chat. Supports text and rich message types.
`lark.lark_list_members`	Read	chat_id, page_size, page_token	List members of a specific Lark chat. Returns member IDs, names, and roles.
`lark.lark_get_current_user`	Read	none	Get information about the currently authenticated Lark user, including name, user ID, and avatar.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Lark Suite CLI Pages

CI Lark Suite CLI for CI. Cron Jobs Lark Suite CLI for cron jobs. Shell Scripts Lark Suite CLI for shell scripts. Coding Agents Lark Suite CLI for coding agents.