Skip to main content
Glama
meilSop

YApi MCP Server

by meilSop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to YApi MCP Server

No user-submitted related servers found.

    Related Servers

    • YAPI MCP Server

      zhhbinn
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to manage YAPI API documentation by providing tools to create, update, and retrieve interface details. It also supports running automated tests and managing API data across multiple configured projects.
      11
      9 npm
      MIT

    • YApi MCP Server

      KO-Good-code
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and searching API documentation from YApi instances, allowing AI models to access interface definitions, project API lists, and search through API endpoints using YApi URLs or project IDs.
      8 npm
      MIT

    • RAP2 MCP Server

      MarveleE
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI assistants to access and search RAP2 API documentation, allowing users to query interface details, search APIs by keywords, and retrieve repository interfaces through natural language.
      7
      7 npm
      -

    • YAPI MCP PRO

      guocong-bincai
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables direct interaction with YApi API management platforms from AI editors like Cursor and Claude Desktop, providing complete interface lifecycle management including browsing, creating, updating, and deleting API documentation.
      11 npm
      22
      MIT
    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

    C2.8/5.0

    Scored across 6 tools

    Disambiguation1/5

    Each unique functionality is duplicated with two nearly identical tools (e.g., get_api_list and yapi_list_interfaces). The descriptions are exactly the same, leaving no way for an agent to distinguish between them, which will cause misselection.

    Naming Consistency2/5

    Naming is inconsistent: some tools use a 'get_' prefix (get_api_list, get_api_detail), while others use a 'yapi_' prefix with a different verb order (yapi_list_interfaces, yapi_get_interface_detail). There is no discernible uniform pattern.

    Tool Count2/5

    While the raw count is 6, this is inflated by exact duplicates. The server effectively exposes only 3 unique tools, and the redundancy suggests a lack of curation, making the count feel padded rather than purposeful.

    Completeness2/5

    The tool surface is limited to read-only operations: list, detail, and search. There are no create, update, or delete operations, which are essential for a complete API management workflow, leaving significant gaps for agent tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources