Skip to main content
Glama
saurav61091

mcp-openapi-runner

by saurav61091
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-openapi-runner

No user-submitted related servers found.

    Related Servers

    • FastMCP OpenAPI

      Agarwal-Saurabh
      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

    • FastMCP Gateway

      4human-ai
      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.
      -

    • OpenAPI to MCP

      procoders
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts any OpenAPI specification or Postman Collection into an MCP server, enabling AI assistants like Claude to directly interact with REST APIs without writing any code.
      Apache 2.0

    • openapi-to-mcp

      Karlangas12
      A
      license
      Not graded
      quality
      B
      maintenance
      Converts any OpenAPI 3.x spec into a live MCP server, making every endpoint a validated tool that AI agents can call without writing glue code.
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: list_endpoints is for discovery and metadata retrieval, while call_endpoint is for executing operations. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with clear, descriptive names (list_endpoints and call_endpoint). The naming convention is uniform and predictable throughout the set.

    Tool Count2/5

    With only 2 tools, this server feels thin for its purpose of interacting with an OpenAPI specification. While it covers basic discovery and execution, it lacks tools for more advanced operations like schema inspection, parameter validation, or response handling, making the scope appear underdeveloped.

    Completeness3/5

    The toolset provides a minimal viable surface for calling endpoints and listing them, but there are notable gaps. For example, it lacks tools for managing authentication, handling different HTTP methods explicitly, or validating requests against the OpenAPI schema, which could limit agent effectiveness in complex scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources