A
licenseNot graded
qualityNot graded
maintenanceAutomatically converts Swagger/OpenAPI specifications into dynamic MCP tools, enabling interaction with any REST API through natural language by loading specs from local files or URLs.
-
Swagger MCP Server
by zidong0822
Related Servers
Alternatives to Swagger MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceDynamically converts any Swagger 2.0 or OpenAPI 3.x specification into callable MCP tools, enabling AI clients to interact with API endpoints.17 npmMIT
- AlicenseNot gradedqualityCmaintenanceConverts any OpenAPI/Swagger API specification into MCP tools that AI assistants can use to interact with the API.14 npm7MIT
- AlicenseNot gradedqualityBmaintenanceTurns any OpenAPI/Swagger API into MCP tools, enabling AI assistants to call REST API endpoints directly.2MIT
- -licenseNot gradedqualityNot gradedmaintenanceDynamically generates MCP tools from Swagger/OpenAPI specifications by extracting swagger.json files at runtime. Enables natural language interaction with any REST API that has Swagger documentation.-
- AlicenseNot gradedqualityDmaintenanceConverts any REST API into MCP-compatible tools instantly by providing an OpenAPI/Swagger spec, enabling seamless integration with AI agents.MIT
TDQS
B3.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap. 'api_list_endpoints' lists available endpoints, 'api_get_endpoint_info' provides details for a specific endpoint, and 'api_call' performs actual API calls. The descriptions clearly differentiate their functions, making misselection unlikely.
Naming Consistency5/5
All tools follow a consistent 'api_verb_noun' naming pattern (api_list_endpoints, api_get_endpoint_info, api_call). The structure is uniform throughout, using snake_case and starting with 'api_' as a prefix, which enhances predictability and readability.
Tool Count3/5
With only 3 tools, the set feels thin for a server named 'Swagger MCP Server', which implies broader API documentation or management capabilities. While the tools cover basic operations (list, get info, call), the scope suggests more tools might be expected for comprehensive API interaction, such as schema validation or endpoint testing.
Completeness4/5
The tools provide a logical workflow: list endpoints, get endpoint details, and make API calls, covering core operations for interacting with an API. However, there are minor gaps, such as no tools for managing API schemas, authentication, or error handling, which could limit advanced use cases but are workable for basic needs.
Maintenance
ActivityInactive
ResponsivenessNo issues