OpenAPI REST MCP Server
Related Servers
Alternatives to OpenAPI REST MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to discover and call any REST API from an OpenAPI/Swagger spec or Postman collection at runtime, with authentication, workflows, and prebuilt registry support.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and other MCP clients to interact with any OAuth2-authenticated OpenAPI-based API through automatic tool generation from OpenAPI specifications, with built-in token management and authentication handling.7 npm3MIT
- AlicenseAqualityDmaintenanceA service that dynamically generates MCP tools from Swagger/OpenAPI documentation, allowing Claude Desktop to directly invoke REST APIs through natural language.510 npmMIT
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI/Swagger or REST API into callable MCP tools for Claude, ChatGPT, Copilot, and Cursor, with secure authentication and role-based access control.11 npm1AGPL 3.0
- AlicenseAqualityCmaintenanceEnables interaction with any REST API through token or login authentication, with automatic Swagger/OpenAPI documentation integration for endpoint discovery and comprehensive HTTP request support.7MIT
- AlicenseNot gradedqualityDmaintenanceDynamically generates MCP tools from OpenAPI specifications, enabling AI assistants to interact with any REST API through natural language. Supports multiple APIs with authentication, parameter validation, and integration with Claude Desktop and LangChain.1MIT
TDQS
Scored across 12 tools
Tools are mostly distinct: HTTP methods are separate, Swagger exploration tools have clear purposes (summary vs list vs detail vs schema). Minor ambiguity exists between swagger_fetch (summarize docs) and swagger_list_endpoints (list endpoints), but descriptions resolve it.
Most tools follow a resource_action pattern (api_get, swagger_fetch, config_status). inspect_login breaks the pattern by putting the verb first, but the overall convention is still readable and predictable.
12 tools is well within the ideal range for a REST/OpenAPI server, with no redundancy. Each tool serves a distinct need from documentation exploration to HTTP requests and configuration.
The tool surface covers the full workflow: fetching OpenAPI docs, discovering endpoints and schemas, performing all standard HTTP methods, handling login/token discovery, and managing configuration. No obvious dead ends.