swagger-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| init_projectB | Create .swagger-mcp/config.json and cache directory in the requested workspace. |
| list_servicesA | List configured Swagger services and local cache state. This never fetches remote documents. |
| add_serviceB | Add a named Swagger/OpenAPI source. It does not fetch the document. |
| update_serviceB | Update a service URL. It does not fetch the document. |
| remove_serviceB | Remove a service from config. Existing cached document is preserved. |
| refresh_serviceB | Explicitly fetch one remote Swagger/OpenAPI JSON document and overwrite only its local cache. |
| refresh_all_servicesB | Explicitly refresh every configured service. This is the only bulk network operation. |
| search_operationsB | Search operations only in the local cached document. It never fetches remote Swagger. |
| get_operationC | Read one cached operation by operationId, or by method and path. |
| get_schemaC | Read and resolve one schema from a cached Swagger/OpenAPI document. |
| generate_request_exampleC | Generate curl, axios, or fetch code from one cached operation. |
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 11 tools
Each tool targets a clearly distinct action: project setup, service configuration, remote fetching, local search/retrieval, and code generation. Overlap is minimal; refresh_service and refresh_all_services differ explicitly by scope, and search_operations vs get_operation is unambiguous.
All tool names follow a consistent snake_case verb_noun pattern, such as init_project, list_services, refresh_service, and get_operation. No deviations or mixed conventions are present.
With 11 tools, the set is well-scoped for managing Swagger/OpenAPI services, covering setup, service CRUD, refresh, search, retrieval, and example generation without redundancy.
The tool surface covers the full lifecycle: project initialization, service add/update/remove/list, explicit local and bulk refresh, operation search and retrieval, schema resolution, and request example generation. No obvious gaps exist for the stated purpose.