alidocs-web-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
} |
| logging | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pairing_codeA | 返回把「当前浏览器里已打开的钉钉文档页面」接到本 bridge 所需的配对码（一串字符串数据）。
用法：agent 在目标页面所在的浏览器上下文里执行控制台命令建连——
在该页面（通常是文档 iframe 的 contentWindow）调 |
| get_bridge_statusA | 返回 bridge 当前状态：监听端口、是否已建桥、页面 MCP 会话是否就绪、在途请求数、Origin 白名单、写权限开关。工具调用失败时先查这里。 |
| revoke_sessionA | 轮换配对码并断开当前页面会话（S11）。撤销后旧配对码立即失效，页面 sessionStorage 里的旧值无法再重连，需重新调用 get_pairing_code 配对。用于结束一次授权或怀疑配对码泄露时。 |
| call_page_toolA | 显式按名字调用一个由已建桥页面提供的文档工具。 适用场景：部分 MCP host 在 server 启动后不会刷新 tools/list（不响应 notifications/tools/list_changed）， 因此页面配对后新出现的 read_document / insert_blocks 等工具对 host 不可见。 call_page_tool 恒定出现在 tools/list 中，它只按 name 与 arguments 原样转发给页面， 桥仍不理解工具语义（A10 哑管道约束）。 未建桥时返回 PAGE_NOT_CONNECTED。 |
| list_page_toolsA | 返回「当前已建桥页面」提供的文档工具清单（名字、描述、参数 schema），只读、以数据返回。 适用场景：部分 MCP host 不会随 notifications/tools/list_changed 刷新 tools/list， 导致页面配对后新出现的工具不可见。此时先用 list_page_tools 发现有哪些工具及其参数， 再用 call_page_tool 按名调用。未建桥时返回 PAGE_NOT_CONNECTED。 |
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 5 tools
Each tool targets a distinct aspect of the bridge lifecycle: status, pairing, revocation, discovery of page tools, and forwarding calls. There is no meaningful overlap between them, even though get_bridge_status and list_page_tools both return state—they report on different layers (bridge vs. page-provided tools).
All tool names follow the same snake_case verb_noun pattern: get_bridge_status, get_pairing_code, revoke_session, call_page_tool, list_page_tools. The verbs are specific and the nouns clearly indicate the target, making the naming fully predictable.
Five tools is well-scoped for a bridge-focused MCP server. Each tool covers a necessary part of the pairing/connection/call lifecycle without redundancy or bloat, and the count aligns with the server's narrow purpose.
The tool surface covers the full bridge lifecycle: obtaining a pairing code, checking status, revoking sessions, enumerating page-provided tools, and invoking them. There are no obvious dead ends—even hosts that don't refresh tool lists are supported via call_page_tool and list_page_tools.