Skip to main content
Glama
kardaj

openapi-tools-mcp

by kardaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openapi-tools-mcp

No user-submitted related servers found.

    Related Servers

    • @mcpx-digital/openapi

      TheoryofShadows
      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

    • Swagger MCP

      yangyaofei
      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

    • swagger-api-mcp-server

      NekoTarou
      A
      license
      A
      quality
      C
      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
      12 npm
      1
      MIT

    • swagger-mcp

      emreycolakoglu
      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
      6 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources