@kedoupi/yapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time to live in seconds | 300 |
| LOG_LEVEL | No | Log level (e.g., info) | info |
| YAPI_BASE_URL | Yes | Your YApi base URL | |
| YAPI_PROJECT_TOKEN | Yes | Your YApi project token |
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_get_projectsA | Get list of available YApi projects |
| yapi_get_categoriesC | Get categories for a specific project |
| yapi_get_interfaceC | Get detailed information about a specific API interface |
| yapi_search_interfacesC | Search for API interfaces with various filters |
| yapi_create_interfaceC | Create a new API interface |
| yapi_update_interfaceC | Update an existing API interface |
| yapi_delete_interfaceB | Delete an API interface by ID |
| yapi_create_categoryC | Create a new API category |
| yapi_get_interface_menuA | Get interface menu list with category structure |
| yapi_list_category_interfacesB | Get interfaces within a specific category |
| yapi_import_dataB | Import interface data from external sources |
| yapi_clear_cacheA | Clear the internal cache to force fresh data retrieval |
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 12 tools
Most tools target distinct resources/actions (projects, categories, interfaces). Some overlap exists between get_interface_menu, get_categories, and list_category_interfaces, but descriptions and parameter differences likely clarify their unique purposes.
All tool names follow a consistent yapi_verb_noun pattern (e.g., get_projects, create_interface, delete_interface). Minor variations like get_interface_menu vs get_categories still adhere to the same verb_noun structure, making the naming predictable.
With 12 tools, the server is well-scoped for an API management platform. Each tool covers a meaningful operation without unnecessary redundancy, fitting the ideal range for a focused MCP server.
The interface lifecycle is well-covered (create, read, update, delete, search, list). Minor gaps exist such as lack of project update/delete or category delete, but core workflows are operational and import/cache support adds practical utility.