Yapi Mcp

Created By
tianlu7 months ago
这是一个 Model Context Protocol (MCP) 服务器,用于与 YApi 接口管理平台集成,支持自动生成 TypeScript 类型定义、Mock 数据和 API 请求代码。
Overview

What is Yapi Mcp?

Yapi Mcp is a Model Context Protocol (MCP) server designed for integration with the YApi interface management platform, enabling automatic generation of TypeScript type definitions, mock data, and API request code.

How to use Yapi Mcp?

To use Yapi Mcp, install the server using the command npx -y @vtian/yapi-mcp-server --stdio, configure your yapi.config.json file with the necessary parameters, and utilize the provided MCP tools to interact with YApi data.

Key features of Yapi Mcp?

  • Automatic reading of project configuration files.
  • Fetching complete interface information from YApi with caching support.
  • Generation of TypeScript interface definitions based on response schemas.
  • Intelligent generation of mock test data.
  • Automatic generation of Axios or Fetch style API request functions.
  • Smart caching mechanism to reduce network requests.

Use cases of Yapi Mcp?

  1. Automatically generating TypeScript types for API responses.
  2. Creating mock data for testing purposes.
  3. Simplifying API request code generation for frontend applications.

FAQ from Yapi Mcp?

  • Can Yapi Mcp work with any YApi project?

Yes! Yapi Mcp is designed to integrate seamlessly with any YApi project that provides the necessary configuration.

  • Is Yapi Mcp free to use?

Yes! Yapi Mcp is open-source and free for everyone to use.

  • How does the caching mechanism work?

Yapi Mcp caches YApi data for 30 minutes to minimize network requests and improve performance.

Server Config

{
  "mcpServers": {
    "yapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vtian/yapi-mcp-server",
        "--stdio"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
tianlu
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago