swagger-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_DOCS_URL | No | Default URL or path to an OpenAPI/Swagger specification document. If set, the 'spec' parameter can be omitted in tool calls. |
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 |
|---|---|
| get_api_overviewA | Top-level API metadata: title, version, description, servers, global security, and counts. Start here on an unfamiliar API. |
| list_tagsA | List the API's tags (logical groups) with descriptions and endpoint counts. |
| list_endpointsA | Compact index of endpoints (method, path, summary, tags). Optionally filter by tag. |
| search_endpointsA | Substring search over endpoint path, summary, description, tags, and parameter names. Returns matches ranked by relevance. |
| list_schemasA | List named component/definition schemas with one-line descriptions. |
| search_schemasA | Substring search over schema names, property names, and descriptions. Returns matches ranked by relevance. |
| get_endpointA | Full detail for one endpoint: parameters, request/response schemas, and required auth. Named schemas are shown by name — resolve them with get_schema. |
| get_schemaA | Resolve one named schema. Nested named schemas are shown as { "$schema": "Name" } markers — call get_schema again to expand them. |
| get_authA | Full security schemes for the API (OAuth2 flows, scopes, API-key locations) plus the global security requirement. |
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 9 tools
Each tool has a clearly distinct purpose: API metadata, auth, endpoint details, schema resolution, listings of endpoints/schemas/tags, and searching. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_api_overview, list_endpoints, search_schemas), making them predictable and easy to understand.
With 9 tools, the set is well-scoped for an API exploration server. Each tool serves a necessary function without redundancy or unnecessary complexity.
The tool surface covers the full exploration workflow: overview, auth, listing endpoints/schemas/tags, detailed endpoint and schema retrieval, and substring search. No obvious gaps for the intended purpose.