Skip to main content
Glama
amrsa1

Swagger MCP Server

by amrsa1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Swagger MCP Server

No user-submitted related servers found.

    Related Servers

    • OpenAPI Schema Explorer

      kadykov
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.
      169 npm
      76
      MIT

    • openapi-mcp

      ceski23
      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

    • proratia-mcp

      d3bn
      F
      license
      Not graded
      quality
      C
      maintenance
      A generic MCP server that fetches OpenAPI/Swagger specs from any target API, with auto-discovery and Docker containerization.
      -

    • REST API MCP Server

      nifetency
      A
      license
      Not graded
      quality
      D
      maintenance
      A dynamic MCP server that automatically discovers and generates tools from any REST API using OpenAPI/Swagger specifications, enabling instant endpoint access with zero manual configuration.
      MIT

    • MCP-QA

      qa-reysser
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for the comprehensive analysis of Swagger 2.0 and OpenAPI 3.x contracts. It allows users to extract detailed information about endpoints, request/response schemas, parameters, and security configurations from API documentation.
      -
    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.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: fetching documentation, listing endpoints, getting endpoint details, executing requests, and validating responses. The descriptions make it easy to tell them apart, and there is no ambiguity in their functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., execute_api_request, fetch_swagger_info). The naming is uniform and predictable, using snake_case throughout without any deviations or mixed conventions.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of interacting with Swagger/OpenAPI documentation and executing API requests. Each tool serves a specific role in the workflow, and the count is neither too sparse nor excessive for the domain.

    Completeness5/5

    The tool set provides complete coverage for the Swagger/OpenAPI domain: it supports fetching documentation, discovering endpoints, getting details, executing requests, and validating responses. There are no obvious gaps, and agents can perform a full lifecycle from discovery to execution and validation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources