Skip to main content
Glama
Gorvey

YAPI Interface MCP Server

by Gorvey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to YAPI Interface MCP Server

No user-submitted related servers found.

    Related Servers

    • Contextual MCP Server by ContextualAI

      Contextual MCP Serverofficial

      ContextualAI
      F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides Retrieval-Augmented Generation capabilities using Contextual AI, enabling AI interfaces like Cursor IDE and Claude Desktop to query domain-specific knowledge with context-aware responses and source citations.
      1
      21
      -

    • MCP Expert Server

      crazyrabbitLTC
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.
      11 npm
      3
      MIT

    • 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

    • YAPI MCP Server

      zjlgdx
      F
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server for interacting with a YAPI instance, enabling LLMs to list, search, and retrieve detailed API documentation from YAPI projects.
      24 npm
      -
    • CodeAlive MCP by CodeAlive-AI

      CodeAlive MCPofficial

      CodeAlive-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
      90
      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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching YAPI interface details by ID.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'yapi-get-interface' follows a clear verb_noun pattern and is descriptive.

    Tool Count2/5

    A single tool is too few for a server named 'YAPI Interface MCP Server', which implies a broader scope for managing YAPI interfaces. This minimal set severely limits functionality and suggests an incomplete implementation.

    Completeness1/5

    The tool set is severely incomplete for the domain of YAPI interface management. It only provides a 'get' operation, lacking essential CRUD operations like create, update, delete, or list interfaces, which are necessary for basic agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources