OpenAPI Gateway FAQs

Question 1

Can it integrate multiple APIs?

Accepted Answer

Yes, it functions as a single gateway capable of aggregating multiple OpenAPI APIs. You can configure various upstream APIs, each exposed as a separate MCP endpoint, all managed under one HTTP server.

Question 2

What is the OpenAPI Gateway?

Accepted Answer

The OpenAPI Gateway is a powerful tool that transforms any OpenAPI specification into a fully functional MCP (Multi-Component Protocol) server endpoint, simplifying the process of exposing existing APIs to MCP clients.

Question 3

Does it support MCP service discovery?

Accepted Answer

Yes, it provides MCP service discovery through a standardized `/.well-known/mcp.json` endpoint. This allows MCP clients to easily find and connect to all the configured MCP servers exposed by the gateway.

Question 4

Is it easy to deploy and configure?

Accepted Answer

Absolutely. The OpenAPI Gateway supports containerized deployment with Docker, ensuring easy setup and portability. Configuration is managed through a simple `config.yaml` file, defining API specifications and authentication modes.

Question 5

How does OpenAPI Gateway handle authentication?

Accepted Answer

It offers configurable authentication forwarding, including 'bearer_passthrough' which securely copies the caller's Bearer token directly to the upstream API requests. A 'none' option is also available for APIs requiring no authentication.

OpenAPI Gateway

OpenAPI Gateway

Key Features

Use Cases

Key Features

Use Cases