A
licenseA
qualityC
maintenanceMCP server for reading, writing, and organizing API documentation in Apidog.
12
6 npm
MIT
@lstpsche/apidog-mcp
by lstpsche
Related Servers
Alternatives to @lstpsche/apidog-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityCmaintenanceMCP server for executing MySQL SQL, managing Apifox API documentation, and parsing/executing curl commands.614 npmISC
- AlicenseAqualityCmaintenanceMCP server that provides tools for exploring and testing APIs through Swagger/OpenAPI documentation.5177 npm12MIT
- AlicenseCqualityCmaintenanceAn MCP server that integrates Apifox API documentation with AI assistants, allowing AI to extract and understand API information from Apifox projects.218 npmISC
- FlicenseNot gradedqualityDmaintenanceAn MCP server for the comprehensive analysis of Swagger 2.0 and OpenAPI 3.x contracts. It allows users to extract detailed information about endpoints, request/response schemas, parameters, and security configurations from API documentation.-
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation5/5
Each tool targets a distinct operation, whether it's a specific export format (OpenAPI vs curl vs Postman vs Markdown), a single endpoint vs bulk operation, or schema vs endpoint management. The descriptions clearly differentiate overlapping concepts like update vs bulk_update and delete vs wipe.
Naming Consistency4/5
All tools share the 'apidog_' prefix, which provides strong consistency. However, the pattern is not strictly verb_noun: modules, folders, pipeline, and diff are noun-style names, while most others are verbs or verb_noun. This minor inconsistency keeps it from a perfect score.
Tool Count4/5
22 tools is on the heavier side but appropriate for a feature-rich Apidog API management server covering endpoints, schemas, imports/exports, testing, analysis, and bulk operations. Each tool serves a clear purpose, so the count feels justified rather than bloated.
Completeness4/5
The surface covers most of the core Apidog workflows: endpoint CRUD, schema CRUD, multiple export formats, OpenAPI import, testing, diff/analyze, and bulk updates. Minor gaps include no direct endpoint creation tool (though import_openapi and pipeline handle it) and no tool for listing test scenarios/folders.
Maintenance
ActivityInactive
ResponsivenessNo issues