Skip to main content
Glama
frontzhm

yapi-mcp-bridge

by frontzhm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to yapi-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • YApi MCP Server

      kales0202
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with YApi API management platform through natural language, allowing automated interface management including creating/updating APIs, managing categories, importing data, and retrieving project information.
      9 npm
      9
      GPL 3.0

    • 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-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
      -

    • yapi-mcp

      hizml
      A
      license
      A
      quality
      B
      maintenance
      Exposes YApi's API management capabilities to MCP clients, enabling operations like listing projects, categories, searching APIs, and managing API details.
      5
      6 npm
      2
      MIT

    • 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.
      8 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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: project details, interface retrieval by ID, category listing, interface listing (all or by category), search, and CRUD for categories/interfaces. The overlap between list_interfaces and list_category_interfaces is resolved by clear filtering semantics, so no ambiguity exists.

    Naming Consistency5/5

    All tools follow a strict 'yapi_<verb>_<noun>' pattern using snake_case (e.g., yapi_get_project, yapi_create_interface). The verb-noun ordering is uniform, and each name clearly reflects the operation and resource, making the set highly predictable.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a YApi bridge covering project info, category management, and interface lifecycle. Each tool serves a distinct purpose without redundancy, and the count falls comfortably within the ideal 3-15 range.

    Completeness3/5

    The surface covers create, read, and update for interfaces, plus create and list for categories, but lacks delete operations for both interfaces and categories. This is a notable gap for full lifecycle management, though the core workflows (viewing, searching, and editing) are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources