YApi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAPI_TOKEN | Yes | YApi access token (Login to YApi → Profile Settings → Copy Token) | |
| YAPI_BASE_URL | Yes | Your YApi server URL |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yapi-get-interfaceB | 根据接口ID获取接口详情 |
| yapi-get-interface-by-urlC | 根据YApi URL获取接口详情，支持格式如：http://localhost:40001/project/11/interface/api/23 |
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 2 tools
The two tools have clearly distinct purposes: one retrieves interface details by ID, while the other retrieves them by URL. There is no overlap or ambiguity between their functions, making it easy for an agent to select the correct tool based on the available input.
Both tools follow a consistent naming pattern: 'yapi-get-interface' with a suffix indicating the input type ('-by-url'). This verb_noun structure is uniform and predictable, enhancing readability and usability across the tool set.
With only 2 tools, the server feels under-scoped for a YApi (API management) domain. This minimal set lacks essential operations like creating, updating, or listing interfaces, which are typical for such systems, making it insufficient for comprehensive agent workflows.
The tool surface is severely incomplete for API management. It only provides retrieval methods (by ID and URL), missing critical CRUD operations such as create, update, delete, or list interfaces. This creates significant gaps that will likely cause agent failures in handling full lifecycle tasks.