A
licenseNot graded
qualityA
maintenanceEnables LLMs to manage Apifox API projects, including listing, creating, updating, and deleting API endpoints and schemas via natural language.
30
MIT
Apifox MCP Pro
Related Servers
Alternatives to Apifox MCP Pro
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.113 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to search and explore API documentation from Apidog projects or OpenAPI/Swagger specifications, providing endpoint details, schemas, and project statistics through natural language queries.628 npm1ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Apifox API documentation via MCP, supporting module-specific dynamic reading, API CRUD, and auditing.-
- FlicenseNot gradedqualityCmaintenanceThis server acts as a Message Communication Protocol (MCP) service for integrating Apifox and Cursor, enabling OpenAPI interface implementation through AI-driven interaction.7-
- AlicenseCqualityDmaintenanceProvides tools for AI assistants to list, search, and get details of YApi interfaces.67 npmISC
TDQS
C2.9/5.0
Scored across 9 tools
Disambiguation2/5
All tools are information retrieval functions with overlapping purposes focused on getting metadata or restriction details about different Apifox features. An agent would struggle to choose between them as they all serve similar descriptive roles rather than distinct operational actions. The boundaries are unclear, with tools like apifox_api_info and apifox_project_info potentially covering similar ground.
Naming Consistency5/5
Tool names follow a highly consistent pattern throughout: all use snake_case with the prefix 'apifox_' followed by a feature name and '_info' or '_access' suffix. This predictable structure makes it easy to understand the naming convention and anticipate tool purposes based on their names.
Tool Count3/5
With 9 tools, the count is reasonable for a documentation/metadata server, but it feels borderline heavy given the narrow scope. All tools serve similar informational purposes rather than covering a broad operational domain, making the set feel somewhat redundant rather than comprehensive for a typical MCP server's action-oriented expectations.
Completeness2/5
The tool surface is severely incomplete for what appears to be an API testing/management domain. While it provides metadata about various Apifox features, it lacks any operational tools for actually using those features (e.g., creating projects, running tests, managing environments). This creates significant gaps that would prevent agents from performing meaningful work beyond information lookup.
Maintenance
ActivityInactive
ResponsivenessNo issues