Skip to main content
Glama
hizml

yapi-mcp

by hizml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to yapi-mcp

No user-submitted related servers found.

    Related Servers

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

    • 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.
      5 npm
      GPL 3.0

    • 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.
      6 npm
      9
      GPL 3.0

    • YAPI MCP Server

      W-Abel-jia
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for the YAPI interface management platform that enables users to manage projects, categories, and API interfaces. It supports querying project details, listing interfaces, and creating or modifying API documentation through natural language.
      9
      2 npm
      3
      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 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing projects, retrieving categories, getting API details, saving APIs, and searching. There is no functional overlap; an agent can clearly distinguish them.

    Naming Consistency5/5

    All tools follow a consistent 'yapi_verb_noun' pattern using snake_case, with clear and descriptive verbs (get, list, save, search). No mixing of conventions.

    Tool Count5/5

    Five tools is well-scoped for a YApi integration, covering the core interactions: project listing, category browsing, API details, creation/updating, and searching. Not excessive or insufficient.

    Completeness4/5

    Core CRUD and search are present, but a delete API tool is missing, which could be a gap for lifecycle management. However, the main workflows (discover, read, create/update) are covered.

    Resources