MCP Server My Lark Doc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OAUTH_HOST | No | OAuth callback server host | localhost |
| OAUTH_PORT | No | OAuth callback server port | 9997 |
| LARK_APP_ID | Yes | Your Lark App ID | |
| LARK_APP_SECRET | Yes | Your Lark App Secret |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_lark_doc_contentC | Get Lark document content |
| search_wikiC | Search Lark Wiki |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves document content by URL, the other searches the wiki by keywords. There is no ambiguity or overlap.
Both tools use a consistent verb_noun pattern with snake_case: 'get_lark_doc_content' and 'search_wiki'. The naming convention is uniform and predictable.
With only 2 tools, the server feels underdeveloped for a document/wiki domain. Typical servers of this scope would include list, create, update, or delete operations, making this minimal.
The tool surface is incomplete for Lark Doc: it only provides content retrieval and wiki search, but lacks essential operations like listing documents, editing, or managing wiki pages. Major gaps exist.