Summary

Covers the write side of YApi, not just reading it.

Most documentation bridges stop at lookup. Here the create, update and upsert calls are all exposed, so an assistant that just wrote a handler can register the matching interface in the same turn. The token is per-project, which keeps the blast radius to one project rather than the whole YApi instance.

What it is

A Node server that wraps the everyday YApi endpoints — projects, categories, interfaces — so an assistant can manage API documentation in your own YApi deployment. Access is scoped by a per-project token, so it only reaches the project whose token you paste in.

What you get

`get_project` returns the project's basic information
`add_cat` creates an interface category; `get_cat_menu` and `list_menu` return the category and interface menus
`list_cat` and `list_interface` list the interfaces under a category or across the project
`get_interface` reads one interface definition in full
`add_interface`, `up_interface` and `save_interface` create, update, or create-or-update an interface
`import_data` pushes a batch of interface data into the project

Requirements

The npm package `mcp-server-yapi`, version 0.1.2, run as `npx -y mcp-server-yapi` on Node.js >= v18.0.0. Set `YAPI_BASE_URL` to your YApi address and `YAPI_TOKEN` to the project token from the project's settings; `MCP_DEBUG_CONSOLE` turns debug output on or off.

Setup effort

One command plus a key — npx -y mcp-server-yapi, then supply credentials