Summary
The spec arrives in the session at the moment the code gets written against it.
The flow the two tools describe is list, then fetch: yapi_get_interfaces takes a url and yapi_get_interface_detail takes an id, which comes from the listing. Both read — nothing here creates or edits an interface, so YApi remains the place a spec changes. Authentication carries YAPI_COOKIE alongside YAPI_TOKEN, which makes a session cookie part of what has to stay valid for the calls to land.
What it is
A read-side YApi client: the interface index for a URL, and the detail for a single interface id.
What you get
- yapi_get_interfaces returns the interfaces found at a YApi url you pass.
- yapi_get_interface_detail returns the full definition of one interface, addressed by its id.
Requirements
A YApi instance at BASE_URL, plus YAPI_TOKEN and YAPI_COOKIE for the account whose view of the project the server reads.
Setup effort
One command plus a key — npx -y auto-yapi-mcp, then supply credentials