Skip to main content
Glama
tiandashu

yapi-mcp-server

by tiandashu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to yapi-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • Swagger MCP Server

      tuskermanshu
      A
      license
      B
      quality
      D
      maintenance
      A server based on Model Context Protocol that parses Swagger/OpenAPI documents and generates TypeScript types and API client code for different frameworks (Axios, Fetch, React Query).
      12
      10 npm
      16
      ISC
    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/5.0

    Scored across 5 tools

    Disambiguation3/5

    The tool names suggest distinct purposes, but without descriptions, boundaries are unclear—especially between generate_types and generate_api_code, which could be seen as overlapping. read_config and get_yapi_data also share a similar 'retrieve data' feel.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (read_, get_, generate_). The verb is always first and nouns are clear, making the naming uniform and predictable.

    Tool Count5/5

    Five tools is within the ideal 3-15 range. Each tool appears to serve a distinct purpose in the YAPI workflow, so the count feels well-scoped without being sparse or bloated.

    Completeness4/5

    The set covers the core YAPI integration workflow: configuration, data retrieval, and generation of types, mocks, and API code. Minor gaps might exist (e.g., no explicit tool for updating or validating data), but the main lifecycle is represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources