Swagger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWAGGER_URL | Yes | The Swagger/OpenAPI target URL to inspect. | |
| SWAGGER_TOKEN | No | Optional bearer token authentication. Takes precedence over basic auth if provided. | |
| SWAGGER_PASSWORD | Yes | Password for basic authentication to the Swagger/OpenAPI endpoint. | |
| SWAGGER_USERNAME | Yes | Username for basic authentication to the Swagger/OpenAPI endpoint. |
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 |
|---|---|
| list_api_modulesB | List all API modules/tags in Swagger. |
| search_apiB | Search API endpoints by module, path, summary or operation ID. |
| get_api_detailsB | Get complete endpoint documentation including parameters, request body and responses. |
| get_api_schemaC | Get request or response DTO schema definitions by schema name. |
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 4 tools
Each tool targets a distinct stage of exploring a Swagger spec: listing modules, searching endpoints, retrieving endpoint details, and fetching DTO schemas. Search vs. get_api_details could superficially overlap, but the descriptions make clear one returns matches while the other returns full documentation for a specific endpoint.
All names use snake_case with verb-first phrasing (list_api_modules, search_api, get_api_details, get_api_schema), which is predictable. The minor deviation is search_api, which omits the noun suffix and breaks the verb_api_noun pattern used by the other three.
Four tools are appropriately lean for a read-only Swagger documentation server, with no redundant entries. It is on the thin side—one more tool (e.g., listing endpoints within a module) would make the surface feel complete rather than minimal.
The core consumption workflow—discover modules, search endpoints, read full details, resolve schemas—is fully covered. Minor gaps remain: no way to enumerate all endpoints in a module without a search query, and no tool for global definitions or servers, but agents can work around these.