Swagger MCP Adapter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEOUT | No | Request timeout in ms | 30000 |
| BASE_URL | No | Base URL for API calls | From OpenAPI spec |
| CACHE_TTL | No | Cache time-to-live in ms | 300000 |
| LOG_LEVEL | No | Logging level | info |
| SWAGGER_PATH | No | Path to OpenAPI/Swagger file | ./swagger.json |
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_servicesB | List all available API services from the Swagger/OpenAPI specification and prepare for caching |
| get_service_informationA | Get comprehensive information about a specific API service including parameters, request/response schemas, and example usage |
| get_all_service_informationA | Get detailed information about all API services from a Swagger/OpenAPI specification including parameters, request/response schemas, and examples |
| get_cache_informationA | Get comprehensive information about the cache status including cached specifications, expiration times, and performance metrics |
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
There is overlap between list_services and get_all_service_information, as both return information about all services, though one is a list and the other provides detailed info. get_service_information and get_cache_information are distinct. Agents might confuse list_services with get_all_service_information when seeking details.
Tool names follow a verb_noun pattern, but mix 'list' (list_services) with 'get' for the others. This is a minor deviation from a fully consistent verb set, but the pattern is still predictable and readable.
Four tools is well-scoped for a Swagger/OpenAPI adapter, covering list, get single, get all, and cache info without unnecessary bloat. The count is within the ideal range and each tool earns its place.
The tool set covers the core operations needed for a Swagger adapter: enumerating services, retrieving details for one or all, and managing cache information. No obvious gaps exist for the stated purpose.