YAPI MCP Server

Example Use Cases

• 1

  Retrieve a project's API interface list (categories, paths, methods, status) to build or validate integration code.

• 2

  Detailed interface specifications (request/response parameters, headers, body schemas) to generate example requests or client stubs.

• 3

  Integrate with a self-hosted YAPI instance (using YAPI_URL and project tokens) to provide up-to-date API documentation during conversations.

Description

This Model Context Protocol (MCP) server exposes YAPI project data (categories, interfaces, and detailed interface specs) to LLMs and agent frameworks. It supports listing interface categories with basic metadata and fetching full request/response schemas and headers for a given interface ID. The server is configured via the YAPI_URL environment variable and uses project tokens for access, and includes usage notes for integration with Claude Desktop. It simplifies programmatic access to YAPI docs so agents can answer API-related questions or generate code against documented endpoints.