Skip to main content
Glama
openapi-tools-mcp

openapi-tools-mcp

by kardaj

Related Servers

Alternatives to openapi-tools-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables local analysis of OpenAPI 3 and Swagger 2 JSON/YAML spec files on disk, with no remote fetching of specs or credentials. It groups endpoints by tag, flags operations that appear to lack security, lists deprecated operations, and produces short markdown cheat sheets for agents.
      4
      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
      Not graded
      quality
      B
      maintenance
      Enables an assistant to read a local OpenAPI 3.x specification, search operations, retrieve endpoint or schema details, and expose documentation through tools, resources, and prompts.
      71 npm
      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
    • 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
      10 npm
      1
      MIT

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    spec_info summarizes the whole spec, spec_list enumerates keys within a section, and spec_get retrieves a specific item. These are distinct operations with clear scope boundaries, though info and get could be slightly confused without the descriptions.

    Naming Consistency5/5

    All three tools use a consistent spec_<action> pattern: spec_info, spec_list, spec_get. The naming is predictable and easy to parse.

    Tool Count5/5

    Three tools are well-suited for a lightweight OpenAPI spec inspection server. Each tool earns its place for summary, enumeration, and retrieval without redundancy.

    Completeness4/5

    The set covers core read-only exploration: summarize, list keys, and get items with optional $ref resolution. Minor gaps such as search, validation, or diff operations exist but are not essential for the apparent inspection purpose.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing