Because both the reading and the writing sides are exposed, the interface definition can be looked up, changed and re-run as a test without leaving the editor — which is the gap that lets YApi drift from the implementation in the first place.
A full-lifecycle connector to a YApi instance. It authenticates with the cookie from your browser session, discovers the projects that cookie can see, and exposes interface, project, category, user and test-collection operations as tools.
- Interfaces — `yapi_get_api_desc`, `yapi_save_api` to add or update, `yapi_search_apis`, `yapi_delete_interface`, `yapi_copy_interface` including across projects
- Projects — `yapi_list_projects`, `yapi_create_project`, `yapi_update_project`
- Categories — `yapi_get_categories`, `yapi_create_category`, `yapi_update_category`, `yapi_delete_category`
- Users — `yapi_get_user_info`, `yapi_get_user_groups`
- Testing — `yapi_get_test_collections`, `yapi_create_test_collection`, `yapi_run_interface` to run an interface test against a chosen environment
- Migration — `yapi_import_swagger` to bring in Swagger data, `yapi_export_project` to take a project out
Your YApi server address in `YAPI_BASE_URL` and a cookie string in `YAPI_TOKEN` that contains both `_yapi_token` and `_yapi_uid` — copy the complete Cookie header out of a request in your browser's Network panel, not a fragment of it. Runs as `npx -y yapi-mcp-pro`, with an SSE mode for server deployments. If the client shows a failed connection, check `npx yapi-mcp-pro --version` prints a version first; when it does not, `npm cache clean --force` is the fix the README puts ahead of everything else. Project information and category lists are cached with a 10 minute default expiry, while interface reads always go live.
One command plus a key — npx -y yapi-mcp-pro, then supply credentials