openapi-md-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAPI_URL | No | Runtime spec URL (priority). Can be a /docs page URL: automatic spec discovery, falls back to same-origin /openapi.json then /openapi.yaml. | http://localhost:8000/openapi.json |
| OPENAPI_FILE | No | Fallback spec file path (used when runtime is unreachable). | |
| OPENAPI_TIMEOUT | No | Fetch timeout in seconds. | 2.0 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_endpointsA | 列出 API 全部端点（方法/路径/摘要表）。了解 API 全貌的第一步；需要细节时用 get_endpoint / get_schema 按键下钻。 |
| get_endpointA | 获取单个端点的 markdown 详情（鉴权、参数、请求体、响应）。method 大小写不敏感；键从 list_endpoints 获得。 |
| get_schemaA | 获取单个 schema 的属性表与嵌套下钻键。schema 名从 get_endpoint 输出的 |
| selectA | 按 glob 模式与鉴权 / tag 过滤批量选中端点键与 schema 名（含鉴权列的键表）。patterns 元素形如 "GET /v1/*"（方法可为 *、大小写不敏感）；零匹配返回可用条件提示。选中后用 get_batch 批量取详情。 |
| get_batchA | 批量获取端点详情与 schema 属性表，引用的 schema 自动整合为共享附录（去重）。keys 混合 "METHOD /path" 端点键与 schema 名（去重后 ≤40 个）；键从 list_endpoints / select 获得。 |
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 5 tools
Each tool is clearly anchored to a distinct stage of the workflow: overview, single endpoint details, single schema details, bulk selection, and bulk retrieval. There is no meaningful overlap between the five operations.
The names mostly follow a clear verb_noun pattern, with list_endpoints for the collection and get_endpoint / get_schema for individual items. The bare 'select' and the somewhat generic 'get_batch' are minor deviations from the otherwise consistent style.
Five tools form a tight, well-scoped set for navigating OpenAPI documents: overview, detail, schema access, filtering, and batch retrieval. Each tool has a clear purpose and none feel redundant.
The main exploration workflow is complete: list endpoints, inspect endpoint and schema details, filter selections, and batch fetch. A dedicated way to enumerate all schemas up front would be a minor improvement, but the select/get_batch flow provides a workable path.