OlympHill
openapi-mcp logo

openapi-mcpDockerized MCP Server to allow your AI agent to access any API with existing api docs

(0)
Daniel NikulshynReviewed by Daniel Nikulshyn·Updated July 2026

Overview

OpenAPI-MCP is a Dockerized MCP server that allows AI agents to access any API with existing OpenAPI or Swagger documentation. It generates MCP tool definitions from a Swagger/OpenAPI specification file, enabling MCP-compatible clients like Cursor to interact with APIs described by standard OpenAPI specifications. This eliminates the need for additional coding to access an API; simply provide its OpenAPI/Swagger specification. The tool supports OpenAPI v2 (Swagger) and v3, creating MCP tool schemas from OpenAPI operation parameters and request/response definitions. It securely manages API key authentication for the proxied API without exposing keys to the MCP client. Key features include automatic tool generation from OpenAPI specifications, flexible API key handling, and the ability to work with local specification files or remote URLs. The tool is easily deployable and runnable as a containerized service with Docker. OpenAPI-MCP allows for secure API key management by injecting API keys into requests based on command-line configuration, loading keys from flags, environment variables, or .env files. It keeps API keys hidden from the end MCP client. The server URL detection feature uses server URLs from the spec as the base for tool interactions, which can be overridden. It also includes filtering options to include or exclude specific operations or tags and allows for custom header injection via the REQUEST_HEADERS environment variable.

Key features

  • OpenAPI v2 (Swagger) and v3 support
  • Schema generation from OpenAPI operation parameters and request/response definitions
  • Secure API key management
  • Server URL detection and filtering options
  • Request header injection

Pricing

Model
Free
Category
MCP Servers
Rating
No reviews yet

Use cases

Enabling AI Agent Access to APIs

Use OpenAPI-MCP to generate MCP tool definitions from an OpenAPI specification, allowing AI agents to interact with APIs without manual coding.

Streamlining API Integration

Leverage existing OpenAPI/Swagger documentation to create MCP tools, reducing integration time and effort.

Pros & Cons

Pros

  • Automatic tool generation from OpenAPI specifications
  • Flexible API key handling and secure management
  • Standard compliance with OpenAPI v2 (Swagger) and v3 support

Cons

  • Requires Docker for deployment
  • May require command-line configuration for API key authentication

Reviews

Sign in to leave a review.

No reviews yet. Be the first!

Q&A

What are the main limitations I should be aware of?

OpenAPI‑MCP requires Docker for deployment and may need command‑line configuration to set up API key authentication, which can add complexity for users unfamiliar with container or CLI workflows.

Asked by Ludovic Girard · Jan 15, 2026

How does OpenAPI‑MCP handle API keys securely?

The server manages API key authentication internally, injecting the keys into proxied requests without exposing them to the MCP client, ensuring that credentials remain hidden from downstream agents.

Asked by Amina Diallo · Dec 1, 2025

Can OpenAPI‑MCP work with both Swagger (v2) and OpenAPI v3 specifications?

Yes, the server supports both OpenAPI v2 (Swagger) and v3 formats, automatically generating MCP tool schemas from the operation parameters and request/response definitions in either version.

Asked by Zeynep Aydin · Oct 23, 2025

How do I deploy OpenAPI‑MCP and what environment does it require?

OpenAPI‑MCP runs as a Docker container, so you need Docker installed on your host. Deploy by pulling the image and starting the container with your OpenAPI/Swagger file mounted or supplied via a volume.

Asked by Chioma Nwosu · Sep 30, 2025

Ask a question

MCP Servers alternatives