Hi Apidog team,
I’m currently using Apidog to maintain both API specifications and other technical documentation (such as network architecture docs, deployment guides, etc.) for our platform.
The MCP server currently only supports API specifications (OpenAPI/Swagger), which is great for development workflows. However, it would be incredibly valuable if the MCP server could also access non-API documentation stored in Apidog projects.
Use Case:
When working with an AI coding assistant, I’d like to reference our architecture documentation alongside API specs. For example: “Refer to our Network Architecture document and suggest how to implement this API endpoint, considering our VPC setup and ECS infrastructure.”
Proposed Solution:
Extend the MCP server to index and provide access to all documentation types within an Apidog project, not just API specifications.
This would make Apidog a true single source of truth for AI-assisted development, combining both API contracts and architectural context.
Is this on your roadmap? Would love to hear thoughts from the community!