openapi-mcp-proxy
Related Servers
Alternatives to openapi-mcp-proxy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceA MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context101 npm49MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.7 npm3MIT
- AlicenseAqualityDmaintenanceA generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.25 npmMIT
- AlicenseAqualityAmaintenanceMCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.762 npm10MIT
- FlicenseBqualityDmaintenanceAn MCP server that crawls and parses OpenAPI JSON or Swagger UI URLs to provide concise endpoint summaries. It enables LLMs to discover and interact with API interfaces by extracting methods, paths, and operation IDs from documentation sources.2-
- FlicenseNot gradedqualityBmaintenanceAn MCP server that dynamically reads OpenAPI specs and registers every endpoint as an LLM-callable tool with automatic change detection and hot reload.1-
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no overlap: adding/removing APIs, listing APIs/endpoints/models, getting API/endpoint/model details, and searching endpoints. The descriptions reinforce this separation, making it easy for an agent to select the right tool.
All tools follow a consistent verb_noun pattern with snake_case (e.g., add_api, list_endpoints, get_model_schema). The verbs (add, get, list, remove, search) are used predictably across the toolset, enhancing readability and predictability.
With 9 tools, this server is well-scoped for managing OpenAPI configurations. It covers core operations like configuration management, listing, and querying without being overly sparse or bloated, ensuring each tool serves a necessary function.
The toolset provides complete coverage for the domain of OpenAPI proxy management: CRUD operations for APIs (add/remove/list), exploration of endpoints and models (list/get/search), and no obvious gaps. Agents can fully interact with saved APIs without dead ends.