A
licenseA
qualityC
maintenanceMCP server for reading, writing, and organizing API documentation in Apidog.
12
6 npm
MIT
apidog-mcp
by ixlammm
Related Servers
Alternatives to apidog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that provides 22 tools to manage Apidog API documentation, including importing OpenAPI specs, exporting, diffing, analyzing, and bulk-editing endpoints.2210 npm3MIT
- AlicenseCqualityCmaintenanceAn MCP server that integrates Apifox API documentation with AI assistants, allowing AI to extract and understand API information from Apifox projects.218 npmISC
- AlicenseAqualityDmaintenanceMCP server for managing Apidog test cases, scenarios, suites, and test data, providing full read/write access to Apidog's test management features.3027 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Apifox API management with read/write/import capabilities.737 npm1MIT
- AlicenseBqualityCmaintenanceMCP server for executing MySQL SQL, managing Apifox API documentation, and parsing/executing curl commands.614 npmISC
TDQS
C2.4/5.0
Scored across 36 tools
Disambiguation2/5
Multiple tools overlap significantly: create_api_detail, add_request, and add_endpoint all create API endpoints; update_api_detail, update_request, update_endpoint, and patch_openapi all handle updates; delete_api_detail, delete_request, and delete_endpoint are near-duplicates. Agents will struggle to choose the correct tool without deep inspection.
Naming Consistency3/5
All tools share a consistent 'apidog_' prefix and snake_case format, mostly following verb_noun. However, there are inconsistencies: 'add' vs 'create' for similar operations, 'get_openapi' is an alias for 'export_openapi', and 'update_module' overlaps with 'rename_module'.
Tool Count2/5
With 36 tools, the surface is too large for a single MCP server. Many tools are aliases or redundant variants (e.g., three creation methods, three update methods, three delete methods), inflating the count without adding distinct capability.
Completeness2/5
The API lifecycle is covered through multiple overlapping paths, but there are notable gaps: no environment CRUD beyond listing, no test case management beyond listing tags/categories, and the export-modify-validate-import cycle suggests missing native mutation endpoints. The surface is broad but not cleanly complete.