YAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAPI_EMAIL | Yes | 登录邮箱 (Login email) | |
| YAPI_BASE_URL | Yes | YAPI 服务器地址 (YAPI server address) | |
| YAPI_PASSWORD | Yes | 登录密码 (Login password) |
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 |
|---|---|
| yapi-get-projectC | 获取 YAPI 项目信息 |
| yapi-get-project-listB | 获取 YAPI 项目列表 |
| yapi-get-categoriesC | 获取项目的接口分类列表 |
| yapi-get-interfaces-by-categoryC | 获取指定分类下的接口列表 |
| yapi-get-interfacesB | 获取项目的所有接口列表 |
| yapi-get-interfaceB | 获取接口详情，支持格式：数字ID |
| yapi-create-interfaceD | 新增 YAPI 接口 |
| yapi-update-interfaceC | 修改 YAPI 接口 |
| yapi-create-categoryC | 新增 YAPI 接口分类 |
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 9 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (categories, interfaces, projects) and actions (create, get, update), making it easy for an agent to select the right tool. For example, yapi-get-interfaces and yapi-get-interfaces-by-category serve different but complementary purposes without overlap.
All tool names follow a consistent pattern: 'yapi-' prefix, followed by a verb (create, get, update), then a noun (category, interface, project). This predictable structure enhances readability and makes the tool set easy to navigate. There are no deviations in naming conventions across the nine tools.
With 9 tools, the server is well-scoped for managing YAPI resources. Each tool earns its place by covering essential operations like listing, creating, and updating interfaces and categories, as well as retrieving project information. This count is appropriate for the domain without being overwhelming or insufficient.
The tool set provides strong coverage for core CRUD operations on interfaces and categories, and project listing. However, there are minor gaps, such as missing update and delete operations for categories and projects, which agents might need to work around. Overall, it supports key workflows but isn't fully comprehensive.