MCP-DOC-MID
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port for SSE/HTTP mode | 3000 |
| LOG_LEVEL | No | Log level: debug, info, warn, or error | info |
| ENABLE_AUTH | No | Enable or disable authentication | true |
| MCP_API_KEY | No | Secret key for API authentication | default-mcp-secret-key |
| SWAGGERS_DIR | No | Directory containing OpenAPI specifications | swaggers |
| DASHBOARD_USER | No | Username for web dashboard access | admin |
| RATE_LIMIT_MAX | No | Maximum requests per rate limit window | 1000 |
| TRANSPORT_MODE | No | Transport mode: stdio, sse, or http | stdio |
| ALLOWED_ORIGINS | No | Allowed origins for CORS | * |
| DASHBOARD_PASSWORD | No | Password for web dashboard access | admin |
| STATS_STORAGE_PATH | No | Path to statistics persistence file | data/stats.json |
| RATE_LIMIT_WINDOW_MS | No | Rate limit window in milliseconds | 900000 |
| STATS_STORAGE_ENABLED | No | Enable persistence of statistics to disk | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_specsA | Lista todas las especificaciones OpenAPI/Swagger (.yml y .json) que han sido aprendidas y dereferenciadas en memoria con sus servidores y versiones. |
| search_docsA | Busca endpoints, operaciones, etiquetas y modelos de datos en todas las especificaciones OpenAPI aprendidas por palabras clave. |
| get_endpoint_docB | Obtiene la documentación completa, parámetros, request body y respuestas dereferenciadas de un endpoint específico. |
| get_schema_docA | Obtiene la definición de un modelo de datos o schema dereferenciado (propiedades, tipos, campos obligatorios y enums). |
| generate_integration_codeB | Genera un snippet/cliente de código listo para producción en TypeScript, JavaScript, Python, cURL o C# para un endpoint específico. |
| get_security_schemesA | Obtiene los esquemas de autenticación y seguridad (Bearer token, API Key, OAuth2) definidos en las especificaciones OpenAPI. |
| validate_payloadA | Valida si un payload JSON cumple con la estructura, campos obligatorios y tipos de datos del schema OpenAPI antes de generar código. |
| query_api_knowledgeB | Consulta y sintetiza el conocimiento transversal de las APIs OpenAPI aprendidas para resolver dudas de negocio o integración. |
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 8 tools
Each tool targets a distinct operation: list, search, get endpoint/schema, generate code, security, validate, and query knowledge. Some potential overlap exists between search_docs and query_api_knowledge, but descriptions clarify the difference between keyword search and synthesized cross-cutting knowledge.
All tool names follow a consistent verb_noun pattern in snake_case, such as list_specs, get_endpoint_doc, and generate_integration_code. There are no mixed casing styles or vague verb variations.
With 8 tools, the count is well-scoped for an OpenAPI documentation assistant. Each tool covers a necessary aspect of browsing, validating, and generating code from specs without redundancy.
The set covers the full document consumption lifecycle: discovering specs, searching content, retrieving endpoint/schema details, understanding security, validating payloads, and generating integration code. No significant gaps are apparent for the server's stated purpose.