Skip to main content
Glama

Related Servers

Alternatives to mcp-api-toolkit

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      A universal MCP server that integrates any API with Claude Desktop by pointing it at a Swagger/OpenAPI spec, automatically generating tools for interaction.
      3
      44
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      A 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 context
      90 npm
      49
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts OpenAPI specifications into MCP servers, allowing tools like Claude Desktop to interact with your REST APIs through a standard protocol.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues