Swagger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWAGGER_URL | Yes | The URL of your Spring Boot Swagger documentation URL. |
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_endpointsA | List all backend API endpoints |
| describe_endpointC | Get details of a backend API |
| generate_frontend_callC | Generate frontend API call code |
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 3 tools
Each tool targets a distinct action: listing all endpoints, describing a specific endpoint, and generating frontend call code. There is no overlap or ambiguity between the tools.
All tools follow a consistent verb_noun pattern with lowercase and underscores: list_endpoints, describe_endpoint, generate_frontend_call. The naming is uniform and predictable.
Three tools is a well-scoped set for a Swagger server focused on endpoint discovery and code generation. Each tool earns its place, covering the core workflow without unnecessary additions.
The tool set covers endpoint listing, description, and frontend call generation, which addresses the primary use case. Minor gaps exist around importing or updating the API specification, but these are outside the apparent read-oriented focus.