wop-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOP_KEYS_DIR | No | 私钥落盘目录(0600 文件) | ./keys |
| WOP_DOC_BASE_URL | No | 文档中心基址 | https://assets.wanlianyida.com/gtsp/platformResource/wop/doc-center |
| WOP_HTTP_TIMEOUT | No | HTTP 超时秒数 | 15 |
| WOP_INDEX_CACHE_TTL | No | llms.txt 索引进程内缓存秒数(0 关闭) | 300 |
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 |
|---|---|
| wop_overviewA | 获取万联易达开放平台(WOP)的接入指南与全部 API 索引。 |
| wop_api_detailA | 获取万联易达开放平台(WOP)指定 API 接口的详细定义。 |
| wop_link_detailA | 获取万联易达开放平台(WOP)文档中心子页面或外部链接的详细内容。 |
| wop_gen_key_pairA | 生成 WOP 对接所需的非对称密钥对(RSA2048 / SM2)。 |
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 4 tools
wop_overview and wop_gen_key_pair are clearly distinct, and wop_api_detail targets API definitions while wop_link_detail targets documentation pages. However, both detail tools accept URLs, so an agent could confuse which one to use for a given link despite the descriptions clarifying intent.
All tools use a consistent wop_ prefix and snake_case, which makes the set predictable. The only minor deviation is that wop_gen_key_pair uses a verb phrase while the other three are noun-oriented, but the pattern remains readable.
Four tools are well-scoped for a WOP integration server: one provides onboarding/index, two retrieve specific docs or API details, and one generates required key pairs. Each tool earns its place without redundancy or excessive surface area.
The server covers the core WOP integration lifecycle: overview/index, API detail lookup, documentation link retrieval, and key generation. Minor gaps exist, such as no standalone search across APIs or direct SDK download tool, but the overview and link tools provide workarounds.