Skip to main content
Glama
Warren-W

Apifox MCP

by Warren-W
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Apifox MCP

No user-submitted related servers found.

    Related Servers

    • Apifox MCP Server

      Errorrrrr
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to import OpenAPI 3 and Swagger 2 formatted JSON data directly into Apifox projects. It provides a tool for automating API documentation management and synchronization through Model Context Protocol clients.
      -

    • Apifox MCP Server

      Juzisuan965
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to fetch and understand API endpoint definitions from Apifox projects in real-time. Supports retrieving complete API specifications including request methods, parameters, headers, and response schemas to improve development efficiency and code generation quality.
      1
      8 npm
      4
      MIT

    • Theneo MCP Server

      atombreak
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automatically create, update, and publish API documentation through Theneo's platform. Supports OpenAPI specs, Postman collections, AI-powered description generation, and natural language interactions for seamless documentation workflows.
      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.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: export_openapi retrieves existing interface information for viewing and planning, while import_openapi adds new OpenAPI/Swagger specifications into the project. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (export_openapi and import_openapi), using the same base noun 'openapi' with descriptive action verbs. This naming scheme is predictable and enhances readability across the tool set.

    Tool Count3/5

    With only 2 tools, the server feels thin for managing Apifox interface documentation, a domain that typically involves more operations like updating, deleting, or searching interfaces. While export and import cover core workflows, the limited count may restrict agent capabilities in handling full lifecycle tasks.

    Completeness2/5

    The tool set is severely incomplete for interface documentation management. It lacks essential CRUD operations such as updating or deleting interfaces, and there are no tools for searching or summarizing beyond the export's summary mode. This creates significant gaps that could lead to agent failures in maintaining a comprehensive project structure.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources