feishu-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lark_cli_runA | Run the official lark-cli with argv-style arguments. Use schema/help first. Set intent=write or auth_config for side-effect commands; those require confirm=true. |
| lark_cli_schemaA | Inspect parameters, request body, response shape, supported identities, and scopes. Call this before API commands or risky writes. |
| lark_cli_helpA | Read help for a service or command. Use before shortcuts because shortcuts are discovered via help. |
| lark_cli_auth_statusA | Check current Feishu/Lark login status, granted scopes, and active identity before calls. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| lark_plan_command | Ask the agent to choose the safest lark-cli command path before execution. |
| lark_safe_write | Guide the agent through schema, dry-run, and confirmation for side-effect work. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| lark-agent-guide | Rules agents should follow when using lark-cli through MCP. |
| lark-command-model | Shortcut, API command, and raw API decision model. |
| lark-skills | Agent-facing domains covered by the official CLI. |
| lark-security | Safety rules for scopes, write commands, HTTP deployment, and Docker state. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: running CLI commands, inspecting schemas, reading help, and checking auth status. No overlap or ambiguity between them.
All tools follow the consistent pattern 'lark_cli_' followed by a descriptive action (run, schema, help, auth_status). Perfectly uniform naming convention.
Four tools is well-scoped for a CLI wrapper server, providing essential operations without unnecessary bloat. Each tool earns its place.
The surface covers running, schema lookup, help, and auth status, which are the core needs for interacting with lark-cli. A minor gap is lack of explicit logout or config tools, but these are workable via lark_cli_run with appropriate arguments.