yapi-mcp-server

Yapi MCP Server

YApi interface definitions become TypeScript types, mock data, and Axios or Fetch request functions through five MCP tools. The project serves frontend developers working with YApi from MCP-compatible clients such as Claude Desktop and Cursor.

Server facts

yapi-mcp-server

Project

Author
tiandashu
License
Not specified

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
4
Last commit
Data as of

Tags

  • api management
  • mcp
  • yapi

Overview

YApi API documentation supplies the schemas behind this project's type, mock, and request-code generation workflows. The read_config tool locates and reads yapi.config.json in a frontend project, while get_yapi_data retrieves interface information from the configured remoteUrl. Retrieved YApi data is cached for 30 minutes. Configuration identifies the platform as yapi and can specify the response data field along with separate output locations for mock files, TypeScript definitions, and API code. These settings connect the project's YApi source to its generated artifacts.

The generation tools address distinct development tasks: generate_types produces TypeScript definitions from interface schemas, generate_mock_from_yapi creates mock data matching those structures, and generate_api_code produces Axios- or Fetch-style request functions. The documented conversational workflows include listing available interfaces, refreshing interface data, and requesting generated outputs for an interface identified by its ID or name. Developers can invoke these tools through MCP-compatible clients, with Claude Desktop and Cursor given as examples. The server uses stdio transport and a Node runtime.

yapi-mcp-server setup notes

  • yapi-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
  • yapi-mcp-server has no recorded license; confirm reuse terms in its repository.

Related MCP servers