swagger-api-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP server host | 0.0.0.0 |
| MCP_PORT | No | HTTP server port | 3000 |
| CACHE_DIR | No | Custom cache directory path | .swagger-cache |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
| SWAGGER_URL | No | Auto-load spec on startup | |
| API_BASE_URL | No | Override API base URL for calls | |
| MAX_SESSIONS | No | Max concurrent HTTP sessions | 100 |
| API_AUTH_TOKEN | No | Initial Authorization header value | |
| SESSION_TIMEOUT_MS | No | HTTP session timeout (30 min) | 1800000 |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| swagger_load_specA | Load and parse a Swagger 2.0 or OpenAPI 3.x specification from a URL. Supports both JSON and YAML formats. The loaded spec is parsed, cached to local JSON files, and used by all subsequent tools. Must be called first before using other tools (unless SWAGGER_URL env var is set). |
| swagger_update_cacheA | Re-fetch the Swagger/OpenAPI spec and rebuild the local file cache. Use this when the upstream spec has changed. Optionally provide a new URL. |
| swagger_get_infoA | Get general metadata about the loaded API specification. Returns a brief summary and the path to info.json which contains full details (title, version, description, servers, authentication schemes, contact info). Use the Read tool on the file path to see complete information. |
| swagger_list_tagsA | List all tags defined in the API spec. Tags are used to group related endpoints. Also shows how many endpoints belong to each tag. |
| swagger_list_pathsA | List all API endpoints with method, path, summary, and tags. Supports filtering by tag, HTTP method, and keyword search. Use pagination (limit/offset) for large APIs. Each entry includes a cacheFile path for detailed info. |
| swagger_get_endpointA | Get a brief summary of a specific API endpoint and the path to its cached JSON file containing complete details (parameters, request body, responses, security). Use the Read tool on the returned file path to see the full endpoint definition. |
| swagger_list_schemasA | List all model/schema definitions in the API spec. Shows schema name, type, description, and property count. Supports keyword filtering and pagination. |
| swagger_get_schemaA | Get a brief summary of a specific schema/model and the path to its cached JSON file containing the complete deep-resolved definition (all properties, types, required fields, enums, defaults, nested structures). Use the Read tool on the returned file path to see the full schema. |
| swagger_searchA | Search across the API specification by keyword. Searches in endpoint paths, summaries, descriptions, operation IDs, and schema names. Returns matching items with their cache file paths for detailed lookup. |
| swagger_call_apiA | Execute an actual HTTP request to an API endpoint. Uses a 2-phase confirmation: first call shows a preview of the request, second call with confirmed=true executes it. Uses the base URL from the spec, API_BASE_URL env var, or the base_url parameter. |
| swagger_set_authA | Dynamically set or clear the Authorization header used by swagger_call_api. The token value is used as-is for the Authorization header (no automatic Bearer prefix). Pass clear=true to remove the current token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| swagger_explore_api | Load and explore an API spec: view info, tags, endpoints, and schemas step by step |
| swagger_find_endpoint | Search for an endpoint by keyword, then show its full details |
| swagger_integrate_api | Find the right endpoint for a task and prepare an API call |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-info | API basic information including title, version, servers, and security schemes |
| api-endpoints | Index of all API endpoints with method, path, summary, and tags |
| api-schemas | Index of all schema/model definitions with name, type, and property count |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NekoTarou/swagger-api-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server