@mhdd_24/api-documentation-mcp
Related Servers
Alternatives to @mhdd_24/api-documentation-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables serving and querying documentation with AI-powered capabilities including markdown file serving, keyword search, and intelligent Q\&A using OpenAI integration.MIT
- FlicenseAqualityCmaintenanceExposes FastAPI reference documentation as MCP tools, enabling LLMs to query FastAPI docs during development for accurate code generation.3-
- FlicenseNot gradedqualityCmaintenanceManages API documentation via Markdown files and exposes it as MCP tools for querying, searching, and updating interface specs, with an admin web UI and REST API.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that converts OpenAPI documentation to Markdown with tolerant parsing, enabling LLMs to batch query and explore APIs.7 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI-powered querying and management of documentation through markdown file serving, keyword search, and OpenAI-based Q\&A capabilities. Supports document indexing, analysis, and agent handoffs with rate limiting protection.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables turning a Hono app into MCP tools and OpenAI-compatible function definitions, either by declaring tools explicitly or by scanning existing routes.2 npmApache 2.0
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: a health check, generating docs from OpenAPI JSON, and generating docs from route lines. The two generation tools are differentiated by their input formats, so an agent can reliably select the right one.
All tools share the same apidoc_ prefix and snake_case style, making the pattern predictable. The minor semantic difference (status vs. from_*) does not undermine consistency.
Three tools is a tight, focused set for a documentation-generation server, with each tool earning its place. No redundant or clearly missing tools appear at this scope.
The server covers health checking and two common documentation source types (OpenAPI JSON and route lines). It lacks features like validation or output customization, but these are minor gaps for a basic doc-generation utility.