Skip to main content
Glama

Related Servers

Alternatives to openapi-mcp-proxy

No user-submitted related servers found.

    Related Servers

    • 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
      101 npm
      49
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      7 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.
      2
      5 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that crawls and parses OpenAPI JSON or Swagger UI URLs to provide concise endpoint summaries. It enables LLMs to discover and interact with API interfaces by extracting methods, paths, and operation IDs from documentation sources.
      2
      -

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: adding/removing APIs, listing APIs/endpoints/models, getting API/endpoint/model details, and searching endpoints. The descriptions reinforce this separation, making it easy for an agent to select the right tool.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., add_api, list_endpoints, get_model_schema). The verbs (add, get, list, remove, search) are used predictably across the toolset, enhancing readability and predictability.

    Tool Count5/5

    With 9 tools, this server is well-scoped for managing OpenAPI configurations. It covers core operations like configuration management, listing, and querying without being overly sparse or bloated, ensuring each tool serves a necessary function.

    Completeness5/5

    The toolset provides complete coverage for the domain of OpenAPI proxy management: CRUD operations for APIs (add/remove/list), exploration of endpoints and models (list/get/search), and no obvious gaps. Agents can fully interact with saved APIs without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues