Skip to main content
Glama
gulbaki

Swagger/OpenAPI MCP Server

by gulbaki

Related Servers

Alternatives to Swagger/OpenAPI MCP Server

No user-submitted related servers found.

    Related Servers

    • 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,157 npm
      294
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that loads multiple OpenAPI specifications and exposes them to LLM-powered IDE integrations, enabling AI to understand and work with your APIs directly in development tools like Cursor.
      7
      51 npm
      90
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools for introspecting and analyzing FastAPI applications, including route discovery, model schema extraction, and source code viewing. It enables users to explore API structures, generate documentation, and debug dependency injection hierarchies through natural language.
      MIT
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      6
      Apache 2.0
    • 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

    TDQS

    D1.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_endpoint_details retrieves specific endpoint information, list_apis enumerates available APIs, load_api loads an API specification, and search_endpoints searches across endpoints. There is no overlap or ambiguity in their functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_endpoint_details, list_apis, load_api, search_endpoints). The naming is uniform and predictable, using snake_case throughout with clear action-object pairs.

    Tool Count3/5

    With only 4 tools, the set feels thin for a Swagger/OpenAPI server, which typically involves operations like validating, updating, or testing APIs. While the core functions are covered, the scope could benefit from additional tools for a more comprehensive API management surface.

    Completeness3/5

    The tools cover basic operations (list, load, get, search), but there are notable gaps for a full API lifecycle, such as creating, updating, or deleting APIs/endpoints, and validating specifications. Agents can perform read and search tasks but may hit dead ends for modification workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues