feishu-access-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEISHU_APP_ID | No | 飞书应用 App ID | |
| FEISHU_APP_SECRET | No | 飞书应用 App Secret | |
| FEISHU_TOKEN_PATH | No | OAuth 令牌文件路径 | ~/.feishu_user_token.json |
| FEISHU_CONFIG_PATH | No | JSON 凭证文件路径 | ~/.feishu_config.json |
| FEISHU_REDIRECT_URI | No | OAuth 回调地址 | http://127.0.0.1:8765/callback |
| FEISHU_BROWSER_PROFILE | No | 浏览器 Profile 目录 | ~/.agent-browser/profiles/feishu |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| feishu_read_resourceB | Read a Feishu wiki, docx, sheet, or bitable URL through API or browser mode. |
| feishu_auth_statusA | Report configured Feishu access paths without exposing secrets. |
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 serve distinct purposes: one reads Feishu resources, the other checks authentication status. There is no overlap, so an agent can easily distinguish them.
Both tools share the 'feishu_' prefix, but 'read_resource' follows a verb_noun pattern while 'auth_status' is more of a noun phrase. The inconsistency is minor given the small set.
With only two tools, the set is at the lower boundary of acceptable size. It is enough for basic read and status checks but feels thin for a general access bridge.
The set lacks crucial operations like listing available resources, writing/updating, or searching. It covers only reading by URL and auth status, leaving significant gaps for a Feishu integration.