A
licenseA
qualityB
maintenanceExposes OpenAPI/Swagger API documentation as MCP tools, enabling AI agents to search, inspect, and call API endpoints through natural language.
5
14 npm
MIT
mcp-swagger
by awssam
Related Servers
Alternatives to mcp-swagger
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceDynamically fetches and exposes OpenAPI/Swagger documentation as tools for AI assistants, enabling them to explore and interact with any REST API.31-
- AlicenseAqualityAmaintenanceConnects AI agents with Swagger/Knife4j API documentation, enabling real-time retrieval, search, and structured understanding of API interfaces, parameters, and schemas.526 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to discover and use Swagger/OpenAPI operations, schemas, and endpoints from configured sources, with optional API request execution and environment-based authentication.40 npm1MIT
- FlicenseNot gradedqualityDmaintenanceBrings OpenAPI/Swagger documentation into AI assistants, enabling endpoint discovery, deep inspection, cURL generation, and TypeScript type generation.-
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.4 npm1MIT
TDQS
A4/5.0
Scored across 14 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: fetching server URLs, executing endpoints, listing endpoints, getting details, searching, schema handling, tag management, API info, security schemes, validation, schema references, curl generation, and deprecated endpoints. The descriptions are explicit enough to prevent confusion even where similar (e.g., listEndpoints vs getEndpointsByTag).
Naming Consistency5/5
All tool names follow a consistent verb+noun camelCase pattern (get, execute, list, search, validate, generate). The style is uniform and predictable, making it easy to infer tool behavior from names.
Tool Count5/5
14 tools is well within the ideal 3-15 range and each tool addresses a specific need in exploring and interacting with a Swagger-defined API. The count feels comprehensive without being bloated.
Completeness5/5
The toolset covers the full lifecycle of API interaction: discovery (list, search, details), execution, schema exploration, security information, validation, and deprecation tracking. There are no obvious dead ends or missing essential operations for a Swagger/OpenAPI use case.
Maintenance
ActivityInactive
ResponsivenessNo issues