@wllcyg/yapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAPI_TOKEN | No | Single project token as fallback (optional) | |
| YAPI_BASE_URL | Yes | The base URL of the YApi server (required) | |
| YAPI_TIMEOUT_MS | No | Timeout in milliseconds (default: 8000) | 8000 |
| YAPI_TOKEN_FILE | No | Path to the token file (default: ~/.yapi-mcp-tokens.json) | ~/.yapi-mcp-tokens.json |
| YAPI_RETRY_COUNT | No | Retry count (default: 1) | 1 |
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 |
|---|---|
| search_yapi_interfacesA | Search YApi interfaces by natural language keyword within a project. Token scope is project-level only. |
| get_yapi_interface_detailA | Get YApi interface detail including request/response schema. Token scope is project-level only. |
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
Search and detail retrieval are clearly distinct stages in the workflow—one identifies interfaces, the other inspects a specific one. No functional overlap exists, so an agent can easily choose the right tool.
Both tools follow a consistent verb_noun pattern with snake_case: search_yapi_interfaces and get_yapi_interface_detail. The verb-first style is uniform and predictable.
With only 2 tools, the server feels minimal for a YApi integration. This is borderline for the rubric's definition of a thin tool set, though it could be defensible if the scope is intentionally limited to read-only search and retrieval.
The read-only workflow is well covered: search for interfaces and retrieve full details. However, there is no way to list all interfaces without a keyword, and no CRUD or project-level operations, which are reasonable gaps for the stated purpose.