Skip to main content
Glama
vp2437
by vp2437

Related Servers

Alternatives to OpenAPI REST MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to discover and call any REST API from an OpenAPI/Swagger spec or Postman collection at runtime, with authentication, workflows, and prebuilt registry support.
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop and other MCP clients to interact with any OAuth2-authenticated OpenAPI-based API through automatic tool generation from OpenAPI specifications, with built-in token management and authentication handling.
      7 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A service that dynamically generates MCP tools from Swagger/OpenAPI documentation, allowing Claude Desktop to directly invoke REST APIs through natural language.
      5
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns any OpenAPI/Swagger or REST API into callable MCP tools for Claude, ChatGPT, Copilot, and Cursor, with secure authentication and role-based access control.
      11 npm
      1
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with any REST API through token or login authentication, with automatic Swagger/OpenAPI documentation integration for endpoint discovery and comprehensive HTTP request support.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Dynamically generates MCP tools from OpenAPI specifications, enabling AI assistants to interact with any REST API through natural language. Supports multiple APIs with authentication, parameter validation, and integration with Claude Desktop and LangChain.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools are mostly distinct: HTTP methods are separate, Swagger exploration tools have clear purposes (summary vs list vs detail vs schema). Minor ambiguity exists between swagger_fetch (summarize docs) and swagger_list_endpoints (list endpoints), but descriptions resolve it.

    Naming Consistency4/5

    Most tools follow a resource_action pattern (api_get, swagger_fetch, config_status). inspect_login breaks the pattern by putting the verb first, but the overall convention is still readable and predictable.

    Tool Count5/5

    12 tools is well within the ideal range for a REST/OpenAPI server, with no redundancy. Each tool serves a distinct need from documentation exploration to HTTP requests and configuration.

    Completeness5/5

    The tool surface covers the full workflow: fetching OpenAPI docs, discovering endpoints and schemas, performing all standard HTTP methods, handling login/token discovery, and managing configuration. No obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues