Skip to main content
Glama

Related Servers

Alternatives to YApi MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      5 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Fetches YApi project API documentation, including normalized JSON request and response schemas and examples, so coding agents can integrate client projects from a pasted YApi URL. Supports interface listing/search, catalog export, and flexible credential configuration.
      7
      MIT
    • 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.
      26 npm
      9
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables direct integration with YApi API documentation platform in MCP-compatible editors like Cursor, allowing users to query API details, list interfaces, and search endpoints by simply pasting YApi URLs.
      5
      10 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables LLM clients to browse and inspect YAPI API documentation, including project info, categories, interfaces, and full API details with request/response schemas.
      7
      10 npm
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves interface details by ID, while the other retrieves them by URL. There is no overlap or ambiguity between their functions, making it easy for an agent to select the correct tool based on the available input.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern: 'yapi-get-interface' with a suffix indicating the input type ('-by-url'). This verb_noun structure is uniform and predictable, enhancing readability and usability across the tool set.

    Tool Count2/5

    With only 2 tools, the server feels under-scoped for a YApi (API management) domain. This minimal set lacks essential operations like creating, updating, or listing interfaces, which are typical for such systems, making it insufficient for comprehensive agent workflows.

    Completeness2/5

    The tool surface is severely incomplete for API management. It only provides retrieval methods (by ID and URL), missing critical CRUD operations such as create, update, delete, or list interfaces. This creates significant gaps that will likely cause agent failures in handling full lifecycle tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues