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
      6 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
      14 npm
      MIT
    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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: retrieving a specific item, summarizing the entire spec, or enumerating keys. There is no overlap in functionality, and an agent can easily select the appropriate tool based on the operation needed.

    Naming Consistency5/5

    All tools follow a consistent 'spec_verb' pattern (spec_get, spec_info, spec_list), which is predictable and makes the tool set easy to navigate.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to reading and exploring OpenAPI specs. Each tool is essential for common tasks, and the count is appropriate for this focused purpose.

    Completeness4/5

    The tools cover core read operations: retrieving specific items, summarizing, and listing keys. Missing operations like validation or diff are not critical for basic spec exploration, so the set feels reasonably complete for its intended use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources