Skip to main content
Glama
ReAPI-com

MCP OpenAPI Server

by ReAPI-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to MCP OpenAPI Server

No user-submitted related servers found.

    Related Servers

    • Swagger/OpenAPI MCP Server

      gulbaki
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.
      4
      10 npm
      14
      ISC

    • OpenAPI MCP Server

      ivo-toby
      A
      license
      Not graded
      quality
      B
      maintenance
      A server that enables Large Language Models to discover and interact with REST APIs defined by OpenAPI specifications through the Model Context Protocol.
      3,228 npm
      294
      MIT

    • openapi-analyzer-mcp

      Sureshkumars
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for analyzing OpenAPI specifications with LLM clients, enabling natural language queries about API structures, endpoints, schemas, and inconsistency detection across multiple specs.
      16 npm
      10
      MIT
    • MockLoop MCP Server by MockLoop

      MockLoop MCP Serverofficial

      MockLoop
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that generates and runs mock API servers from API documentation like OpenAPI/Swagger specs, enabling developers and AI assistants to quickly spin up mock backends for development and testing.
      17
      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

    B3.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. For example, get-api-catalog retrieves metadata, load-api-operation-by-operationId and load-api-operation-by-path-and-method load operations via different identifiers, load-api-schema-by-schemaName loads schemas, refresh-api-catalog updates the catalog, and search-api-operations and search-api-schemas perform distinct searches. The descriptions clarify each tool's unique function, preventing misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with hyphens, such as get-api-catalog, load-api-operation-by-operationId, and search-api-schemas. This predictability makes the set easy to navigate and understand, with no deviations in naming style across the seven tools.

    Tool Count5/5

    With 7 tools, the server is well-scoped for managing OpenAPI specifications. Each tool earns its place by covering essential operations like retrieving, loading, refreshing, and searching metadata, schemas, and operations, without being overly sparse or bloated for the domain.

    Completeness4/5

    The tool surface is nearly complete for interacting with OpenAPI specifications, covering catalog retrieval, operation and schema loading, catalog refreshing, and searching. A minor gap exists in lacking direct update or delete operations for specifications, but agents can work around this by refreshing or reloading as needed, and core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources