yapi-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| read_configD | – |
| get_yapi_dataD | – |
| generate_typesD | – |
| generate_mock_from_yapiD | – |
| generate_api_codeD | – |
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 5 tools
The tool names suggest distinct purposes, but without descriptions, boundaries are unclear—especially between generate_types and generate_api_code, which could be seen as overlapping. read_config and get_yapi_data also share a similar 'retrieve data' feel.
All tools follow a consistent snake_case verb_noun pattern (read_, get_, generate_). The verb is always first and nouns are clear, making the naming uniform and predictable.
Five tools is within the ideal 3-15 range. Each tool appears to serve a distinct purpose in the YAPI workflow, so the count feels well-scoped without being sparse or bloated.
The set covers the core YAPI integration workflow: configuration, data retrieval, and generation of types, mocks, and API code. Minor gaps might exist (e.g., no explicit tool for updating or validating data), but the main lifecycle is represented.