@wllcyg/yapi-mcp
Related Servers
Alternatives to @wllcyg/yapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides tools for AI assistants to list, search, and get details of YApi interfaces.67 npmISC
- AlicenseBqualityFmaintenanceEnables AI tools to search, create, update, and manage YApi API interfaces, projects, and categories through natural language.1216 npm2MIT
- AlicenseAqualityDmaintenanceEnables LLM clients to browse and inspect YAPI API documentation, including project info, categories, interfaces, and full API details with request/response schemas.75 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading and searching API documentation from YApi instances, allowing AI models to access interface definitions, project API lists, and search through API endpoints using YApi URLs or project IDs.6 npmMIT
- AlicenseBqualityDmaintenanceEnables access to YApi interface documentation by retrieving API details through interface IDs or direct YApi URLs.223 npmMIT
- FlicenseAqualityCmaintenanceEnables MCP clients to manage YApi projects and interfaces, including searching and creating APIs, editing mock response bodies and advanced mock scripts, managing mock expectations, and testing mock URLs.111-
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.