swagger-codegen-mcp
Related Servers
Alternatives to swagger-codegen-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables reading and parsing Swagger/OpenAPI specifications to list API endpoints, get detailed endpoint info, search APIs, and generate TypeScript types for request/response.9-
- AlicenseNot gradedqualityFmaintenanceEnables AI to interact with multiple Swagger/OpenAPI specifications by listing endpoints, exploring models, and generating TypeScript code. It centralizes the management of various APIs through a configuration file, allowing for seamless integration of documentation into AI workflows.243 npmMIT
- AlicenseNot gradedqualityDmaintenanceGenerates TypeScript types for API functions from Swagger/OpenAPI documents, enabling AI IDEs to automatically create type definitions.9 npm3MIT
- AlicenseBqualityDmaintenanceA server based on Model Context Protocol that parses Swagger/OpenAPI documents and generates TypeScript types and API client code for different frameworks (Axios, Fetch, React Query).1211 npm16ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI to scan and query local OpenAPI/Swagger documentation, listing API groups and endpoints, and generating TypeScript type definitions for specific endpoints.-
- AlicenseNot gradedqualityDmaintenanceAutomatically parses Swagger/OpenAPI documentation, generates frontend code (Vue3, React, etc.), and enables API testing through natural language commands.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct layer: service discovery, tag listing, endpoint listing, endpoint detail, and code generation. The descriptions make the hierarchy clear, so there is no meaningful overlap between tools.
All tool names follow a consistent snake_case verb_noun pattern: list_* for enumeration, get_ for detail retrieval, and generate_ for code generation. There are no mixed naming styles or vague verbs.
Five tools is well within the ideal scope for a focused Swagger codegen server. Each tool earns its place by contributing one necessary step in the discovery-to-generation workflow.
The set covers the full discovery-to-codegen flow: services, tags, endpoints, endpoint details, and code generation. It lacks whole-service generation and direct schema/model introspection, but agents can work around these by iterating tags or relying on generated code.