OpenAPI MCP Server logo

OpenAPI MCP Server

by MCP-Mirror

This tool creates a Model Context Protocol (MCP) server that acts as a proxy for any API that has an OpenAPI v3.1 specification. This allows you to use Claude Desktop to easily interact with both local and remote server APIs.

View on GitHub

Last updated: N/A

What is OpenAPI MCP Server?

The OpenAPI MCP Server is a proxy that converts OpenAPI endpoints into Claude tools, enabling Claude to discover, understand, and interact with APIs.

How to use OpenAPI MCP Server?

Configure Claude Desktop to use the server by adding it to the mcpServers section in claude_desktop_config.json. Specify the command and arguments to run the server with the path to your OpenAPI specification file. Restart Claude Desktop to start interacting with your API.

Key features of OpenAPI MCP Server

  • Automatic conversion of OpenAPI endpoints into Claude tools

  • File upload support for APIs accepting multipart/form-data

  • Handles API discovery, parameter understanding, and API calls on behalf of Claude

  • Supports OpenAPI v3.1 specifications

Use cases of OpenAPI MCP Server

  • Local API development and testing through natural language

  • Quickly testing and prototyping integrations with third-party APIs

  • Interactive API documentation and exploration

  • Debugging endpoints without writing code

FAQ from OpenAPI MCP Server

What OpenAPI versions are supported?

Currently, only OpenAPI v3.1 specifications are supported.

Does it support remote URLs for file uploads?

No, only local files are supported for file uploads.

What kind of responses are supported?

Response handling is optimized for JSON/text responses.

How are file uploads handled?

File paths are resolved relative to the current working directory, and access is restricted to files the user has permission to read. Large files are streamed directly from disk to the API.

What happens if my OpenAPI spec is causing Claude to crash?

Try running your spec through the spec cleaner app linked in the README.