Skip to main content
Glama
rawveg

OpenAPI Directory MCP Server

by rawveg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to OpenAPI Directory MCP Server

No user-submitted related servers found.

    Related Servers

    • swagger-mcp

      yunhwane
      A
      license
      B
      quality
      D
      maintenance
      Enables natural language exploration of OpenAPI/Swagger specs, allowing users to register APIs, browse endpoints, describe schemas, and detect breaking changes through conversational queries.
      9
      191 npm
      MIT

    • Janus MCP

      DeanWard
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to understand and interact with OpenAPI specifications, providing deep insight into API structures for faster and more accurate API integration.
      9
      7 npm
      1
      MIT

    • mcp-swagger

      awssam
      A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      3 npm
      2
      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

    B3.2/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. The many 'get_' tools target different aspects (API summary vs full details, endpoint details vs examples vs schemas, providers vs provider APIs vs provider services), and cache tools are separate. No two tools are ambiguous.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern in snake_case, with 'get_' for retrieval. However, a few list operations use 'list_' (list_all_apis, list_cache_keys) instead of 'get_', introducing minor inconsistency. Otherwise naming is predictable.

    Tool Count3/5

    With 22 tools, the set is at the upper end of what is reasonable for an API directory server. The tools cover APIs, endpoints, providers, cache, and metrics, but the number feels slightly heavy, bordering on excessive for the domain.

    Completeness4/5

    The server provides comprehensive coverage for querying an API directory: listing, searching, detailed info on APIs and endpoints, provider stats, cache management, and metrics. A minor gap is the lack of a dedicated tool to list API categories (only distribution analysis), but overall the surface is solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources