Skip to main content
Glama
W-Abel-jia

YAPI MCP Server

by W-Abel-jia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to YAPI MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-server-yapi

      YogeLiu
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for YApi that enables LLMs to manage API interfaces, projects, and categories through natural language, supporting multiple projects and path fuzzy matching.
      6 npm
      GPL 3.0

    • Yapi Auto MCP Server

      lzsheng
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for the YApi platform that allows AI assistants to search, create, and manage API documentation directly within tools like Cursor. It supports multi-project management and seamless integration into AI-driven programming workflows for interface maintenance.
      1,706 npm
      120
      MIT

    • yapi-mcp

      geq1fan
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for YApi that enables developers to search, view, create, and update API definitions directly from MCP-compatible IDEs.
      2
      MIT

    • yapi-mcp-zhh

      zhanghaha416
      F
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to manage YApi projects and interfaces, including searching and creating APIs, editing mock response bodies and advanced mock scripts, managing mock expectations, and testing mock URLs.
      11
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (categories, interfaces, projects) and actions (create, get, update), making it easy for an agent to select the right tool. For example, yapi-get-interfaces and yapi-get-interfaces-by-category serve different but complementary purposes without overlap.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'yapi-' prefix, followed by a verb (create, get, update), then a noun (category, interface, project). This predictable structure enhances readability and makes the tool set easy to navigate. There are no deviations in naming conventions across the nine tools.

    Tool Count5/5

    With 9 tools, the server is well-scoped for managing YAPI resources. Each tool earns its place by covering essential operations like listing, creating, and updating interfaces and categories, as well as retrieving project information. This count is appropriate for the domain without being overwhelming or insufficient.

    Completeness4/5

    The tool set provides strong coverage for core CRUD operations on interfaces and categories, and project listing. However, there are minor gaps, such as missing update and delete operations for categories and projects, which agents might need to work around. Overall, it supports key workflows but isn't fully comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources