YAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAPI_BASE_URL | Yes | YAPI server URL, e.g., https://yapi.example.com | |
| YAPI_PROJECTS | Yes | Project configuration in format: projectId1:token1,projectId2:token2. You can get the project token from the YAPI project settings page. |
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 |
|---|---|
| yapi_list_projectsB | 列出所有已配置的 YAPI 项目 |
| yapi_run_auto_testC | 运行 YAPI 自动化测试 |
| yapi_import_dataC | 导入接口数据到 YAPI |
| yapi_interface_addD | 新增接口 |
| yapi_interface_saveC | 保存接口(新增或更新) |
| yapi_interface_upD | 更新接口 |
| yapi_interface_getA | 获取接口详情,可直接传入 YAPI 接口页面 URL 自动解析参数 |
| yapi_interface_listC | 获取接口列表 |
| yapi_interface_list_menuC | 获取接口菜单(包含分类和接口列表) |
| yapi_interface_add_catC | 新增接口分类 |
| yapi_interface_get_cat_menuC | 获取所有接口分类 |
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 11 tools
The tools have clear distinctions for core operations like add, get, list, and save, but there is significant overlap between yapi_interface_add and yapi_interface_save (which handles both add and update), and between yapi_interface_list and yapi_interface_list_menu (both list interfaces with slight variations). This overlap could cause confusion for agents when selecting the appropriate tool.
Most tools follow a consistent yapi_verb_noun pattern (e.g., yapi_interface_add, yapi_interface_get), with clear prefixes and snake_case throughout. However, there are minor deviations like yapi_interface_up instead of yapi_interface_update, and yapi_run_auto_test uses 'run' while others use verbs like 'add' or 'get', slightly breaking the pattern.
With 11 tools, this server is well-scoped for managing YAPI interfaces and projects. The count aligns with the domain's needs, covering operations for projects, interfaces, categories, and testing without being overwhelming or too sparse.
The toolset provides strong coverage for YAPI management, including CRUD operations for interfaces and categories, project listing, and automated testing. A minor gap is the lack of explicit tools for deleting interfaces or categories, which might require workarounds, but core workflows are well-supported.