OpenAPI Proxy FAQs

Question 1

Which AI agents are compatible with OpenAPI Proxy?

Accepted Answer

OpenAPI Proxy is compatible with any MCP client that uses stdio transport, including popular AI agents such as Claude Code, OpenAI Codex, and Gemini CLI. It provides a seamless bridge for these agents to interact with your REST APIs.

Question 2

What OpenAPI versions and formats are supported?

Accepted Answer

OpenAPI Proxy exclusively supports OpenAPI 3.x specifications, available as YAML or JSON files. These can be loaded from local paths or remote HTTP/HTTPS URLs. OpenAPI 2.0 is not directly supported.

Question 3

Does OpenAPI Proxy generate code or require manual updates when my API changes?

Accepted Answer

No. OpenAPI Proxy works by dynamically generating MCP tools at startup from your OpenAPI spec. There is no code generation, no generated files, and no ongoing maintenance required when your API's spec changes.

Question 4

What is OpenAPI Proxy and what problem does it solve?

Accepted Answer

OpenAPI Proxy automatically converts any OpenAPI 3.x specification into a fully functional Model Context Protocol (MCP) server. It eliminates the need to manually write thousands of lines of boilerplate code to create MCP tools for your REST API endpoints, allowing AI agents to use your APIs directly from their OpenAPI specs.

Question 5

How does OpenAPI Proxy handle API authentication?

Accepted Answer

It supports two primary authentication methods: static bearer token authentication (via `MCP_AUTH_TOKEN`) for development, and OIDC PKCE for production, offering browser-based login with automatic token refresh against any OIDC provider.

OpenAPI Proxy

OpenAPI Proxy

Key Features

Use Cases

Key Features

Use Cases