Apifox MCP Server
Related Servers
Alternatives to Apifox MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to manage Apifox API projects, including listing, creating, updating, and deleting API endpoints and schemas via natural language.30MIT
- 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.1,260 npm1ISC
- AlicenseAqualityCmaintenanceEnables AI assistants to query API documentation from Eolink Apikit instances via the Eolink Open API, supporting listing projects, groups, searching APIs by keyword/path, and retrieving detailed API definitions.620 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Apifox API documentation via MCP, supporting module-specific dynamic reading, API CRUD, and auditing.-
- AlicenseAqualityDmaintenanceEnables AI assistants to automatically manage Apifox API documentation by importing OpenAPI/Swagger specifications and exporting existing API structures. Supports batch operations, intelligent deprecation marking, and smart scope detection for partial module imports.233 npm3MIT
- AlicenseAqualityAmaintenanceConnects AI agents with Swagger/Knife4j API documentation, enabling real-time retrieval, search, and structured understanding of API interfaces, parameters, and schemas.513 npm1MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion with other tools. The tool's purpose is clearly defined and distinct by default.
With a single tool, naming consistency is inherently perfect. The name 'get_api_endpoint_info' follows a clear verb_noun pattern and accurately describes its function.
The server has only one tool, which is on the thin side for a typical API integration. While the tool is not trivial, a more comprehensive set (e.g., listing projects or endpoints) would be expected for this domain.
The tool provides a single operation without supporting tools for discovery or listing of projects/endpoints. Agents must already know the projectId and endpointId, which creates a significant gap for autonomous workflows.