eolink-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EOLINK_TOKEN | Yes | Open API 令牌(对应请求头 Eo-Secret-Key) | |
| EOLINK_BASE_URL | Yes | Eolink 实例 Open API 地址,如 https://your-eolink.example.com | |
| EOLINK_NO_PROXY | No | 设 '1' 禁用代理解析(默认自动读 HTTP(S)_PROXY) | |
| EOLINK_SPACE_ID | Yes | 工作空间 ID |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eolink_list_projectsA | 列出当前 Eolink 工作空间下的所有项目(调用 /v2/api_studio/management/project/search)。 不需要参数。返回每个项目的 project_id 和 project_name(以及创建人、是否归档)。 这是使用其它工具前的第一步:拿到目标项目的 project_id,再在 list_groups / search_apis / get_api_detail / export_openapi 调用时显式传入。 |
| eolink_list_groupsA | 列出指定项目下的所有接口分组(含子分组),用于了解接口按业务模块的组织结构。 参数:
返回分组树,每个分组含 group_id、group_name、parent_group_id,子分组在 group_child_list 里。 典型用法:本工具拿到 group_id 后,用 eolink_search_apis 的 group_ids 过滤某模块下的接口。 |
| eolink_search_apisA | 按关键字、分组或状态搜索指定项目里的接口,返回接口列表(api_id、名称、URL、方法、分组等)。 这是查接口最常用的入口。拿到 api_id 后,用 eolink_get_api_detail 获取完整定义。 参数:
返回每个接口的 api_id(后续取详情要用)、api_name、api_path、method、group_name 等。 |
| eolink_find_api_by_pathA | 按接口路径(api_path)精确查找接口,规避 eolink_search_apis 的模糊分词噪声。 内部拉取项目下全部接口后在 server 端按 api_path 匹配,只返回真正匹配的接口。 参数:
返回匹配接口的 api_id、api_name、api_path、method 等。拿到 api_id 后用 eolink_get_api_detail 看完整定义。 |
| eolink_get_api_detailA | 获取单个 HTTP 接口的完整定义:基础信息、请求头、query 参数、restful 参数、请求体参数、响应结构(含 mock 示例)。 参数:
返回 Markdown 格式的接口文档,包含每个参数的名称、类型、是否必填、说明、示例值。 |
| eolink_export_openapiA | 导出指定项目(或指定分组)的接口文档为 OpenAPI/Swagger JSON,适合一次性全量获取。 参数:
注意:全量导出可能很大,会自动按字符上限截断。日常查询单个接口建议用 eolink_search_apis + eolink_get_api_detail。 |
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 6 tools
Each tool targets a distinct operation: listing projects, listing groups, searching APIs, finding by exact path, retrieving detail, and exporting. No two tools overlap in purpose; even the two search-like tools (search_apis and find_api_by_path) use different matching strategies (fuzzy vs exact).
All tool names follow a consistent 'eolink_verb_noun' pattern (e.g., eolink_list_projects, eolink_search_apis). No mixing of camelCase, snake_case, or inconsistent verb styles.
With 6 tools covering project discovery, group navigation, API search and details, and export, the set is well-scoped for an API documentation server. Each tool serves a clear purpose without unnecessary weight.
The tool surface covers the full read lifecycle: discover projects, browse groups, find APIs (by search or exact path), inspect full detail, and export the entire project. No obvious gaps for a consumer of API documentation.