Skip to main content
Glama
Swagger MCP Server

Swagger MCP Server

by tsiva18

Related Servers

Alternatives to Swagger MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.
      11
      15 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.
      9
      97 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Loads and queries OpenAPI/Swagger documents, providing tools to list APIs, get details, search endpoints, and manage schemas for efficient API exploration.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A stdio MCP server that caches Swagger/OpenAPI documents for multiple backend services and provides offline API search, retrieval, and request example generation. It only contacts remote servers when explicitly refreshing the cache.
      11
      5 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to run deterministic security reviews of OpenAPI and Swagger documents, including scanning specs, listing and explaining OWASP-mapped rules, checking authentication coverage, and generating sample audits.
      MIT

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct stage of exploring a Swagger spec: listing modules, searching endpoints, retrieving endpoint details, and fetching DTO schemas. Search vs. get_api_details could superficially overlap, but the descriptions make clear one returns matches while the other returns full documentation for a specific endpoint.

    Naming Consistency4/5

    All names use snake_case with verb-first phrasing (list_api_modules, search_api, get_api_details, get_api_schema), which is predictable. The minor deviation is search_api, which omits the noun suffix and breaks the verb_api_noun pattern used by the other three.

    Tool Count4/5

    Four tools are appropriately lean for a read-only Swagger documentation server, with no redundant entries. It is on the thin side—one more tool (e.g., listing endpoints within a module) would make the surface feel complete rather than minimal.

    Completeness4/5

    The core consumption workflow—discover modules, search endpoints, read full details, resolve schemas—is fully covered. Minor gaps remain: no way to enumerate all endpoints in a module without a search query, and no tool for global definitions or servers, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues