mcp-api-toolkit
Related Servers
Alternatives to mcp-api-toolkit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConverts any OpenAPI/Swagger spec into an MCP server, exposing REST API endpoints as tools for Claude.MIT
- FlicenseAqualityDmaintenanceAn MCP server that lets Claude query, search, and explore OpenAPI specifications from local files. Supports OpenAPI 3.x and Swagger 2.0.4-
- FlicenseAqualityDmaintenanceA universal MCP server that integrates any API with Claude Desktop by pointing it at a Swagger/OpenAPI spec, automatically generating tools for interaction.344-
- AlicenseNot gradedqualityFmaintenanceA MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context90 npm49MIT
- FlicenseNot gradedqualityDmaintenanceAutomatically converts OpenAPI specifications into MCP servers, allowing tools like Claude Desktop to interact with your REST APIs through a standard protocol.-
- AlicenseNot gradedqualityCmaintenanceA generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.20 npmMIT
TDQS
Scored across 8 tools
Most tools have distinct purposes: SDK generation, doc generation, validation, batch testing, parsing, listing, single endpoint testing, and mock data. However, test_api_endpoint and batch_test_endpoints overlap in testing functionality, and validate_api_response and test_api_endpoint both involve validation, which could cause slight confusion.
Tool names are mostly in snake_case with a verb_noun pattern (generate_sdk, generate_api_docs, validate_api_response, etc.). One deviation is parse_openapi (verb_noun but noun is OpenAPI rather than a typical object) and list_endpoints, but overall consistency is high.
With 8 tools, the count is well-scoped for an API toolkit. Each tool corresponds to a distinct, useful operation in the API development lifecycle, and there is no apparent redundancy.
The toolkit covers parsing, listing, testing (single and batch), validation, SDK generation, documentation, and mock data. It misses operations like comparing specs, transforming specs, or generating server stubs, but these are minor gaps for a client-side API toolkit.