mcp-api-translator
Related Servers
Alternatives to mcp-api-translator
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI/Swagger spec into an MCP server, generating one tool per endpoint with zero code.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceGenerate an MCP server for any OpenAPI documented endpoint.332MIT
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI/Swagger specification into a functional MCP server, dynamically exposing API endpoints as LLM tools or generating standalone Python code.MIT
- AlicenseNot gradedqualityBmaintenanceOne command to turn any codebase into an MCP server. Not just REST APIs. Not just OpenAPI specs.55Apache 2.0
- FlicenseNot gradedqualityDmaintenanceDynamically creates an MCP server from any OpenAPI schema, enabling seamless integration with tools like Prompteus and Claude.4-
- AlicenseNot gradedqualityCmaintenanceGenerates production-ready MCP servers from natural language, OpenAPI specs, database schemas, GraphQL schemas, or ontologies.58 npm1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: analyze_spec previews without writing, generate_mcp_server creates a new project, extend_mcp_server appends to an existing one, and list_supported_features reports capabilities. There is no overlap in verbs or intended outcomes, so an agent can easily select the right tool.
All four names follow a strict verb_noun snake_case convention. The generate_mcp_server / extend_mcp_server pair even shares a consistent resource suffix, reinforcing the pattern.
Four tools is well-scoped for a spec-to-MCP-server translator: preview, generate, extend, and capability reporting. Each tool is substantive and earns its place with no redundancy.
The lifecycle is largely covered: inspect a spec, generate a project, aggregate additional specs, and query supported features. Minor gaps exist around updating or regenerating an existing project from a changed spec and removing operations, but agents can work around these via force-based regeneration.