@mhdd_24/api-documentation-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apidoc_statusB | Health check for API Documentation MCP. |
| apidoc_from_openapiC | Generate markdown docs from OpenAPI JSON. |
| apidoc_from_routesC | Document routes listed as method path lines. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.