$ loading_
Let AI agents discover, search, and call REST APIs from OpenAPI specs.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-openapi" yet — see the docs or source repo.
Read this OpenAPI/Swagger document, find the endpoint for creating a customer record, and explain the required authentication, required parameters, and provide one example call.
Returns the matching endpoint, authentication requirements, parameter details, and a sample request.
Using this OpenAPI document, search for all REST APIs related to order lookup and group them by purpose.
Outputs a list of order-related endpoints, grouped by purposes such as detail lookup, listing, and status checks.
Based on this Swagger document, call the endpoint for fetching user profiles. If authentication is required, first explain what auth details and parameters must be provided.
First explains authentication and parameter requirements, then provides the executable API call result or steps.
Developers or product teams can provide an OpenAPI/Swagger document so an AI agent can directly discover and call backend endpoints, reducing manual integration work. It fits systems that already expose standardized API documentation.
When teams need to find available capabilities across multiple API endpoints, this tool helps AI agents search and locate them from the documentation. It is useful when there are many endpoints and the correct call path must be found quickly.
For REST APIs that require authentication and structured parameters, this tool lets AI agents organize calls according to the documentation. It is suitable for automation flows that turn API specs into real requests.
It enables AI agents to discover, search, and call REST APIs described by OpenAPI or Swagger documents. It also supports multiple API endpoints, plus authentication and parameter handling.
The provided information says it supports OpenAPI and Swagger documents. For detailed version compatibility, see the source repository.
Yes. The original description explicitly states support for authentication and parameter handling. For the exact authentication schemes, see the source repository.
Load and explore OpenAPI specs to inspect endpoints, parameters, and schemas.
Turn any OpenAPI API into callable AI tools with authentication support.
Expose OpenAPI endpoints as MCP tools for LLM-driven REST API access.
Search and retrieve API documentation from an internal Swagger platform via MCP.
Scan local OpenAPI docs, query endpoints, and generate TypeScript types.
Connect LLMs to any OpenAPI REST API with natural language.