OpenAPI to Model Context Protocol (MCP)

Created By
gujorda year ago
The OpenAPI to Model Context Protocol (MCP) proxy server bridges the gap between AI agents and external APIs by dynamically translating OpenAPI specifications into standardized MCP tools. This simplifies the integration process, significantly reducing development time and complexity associated with custom API wrappers.
Overview

What is OpenAPI-MCP?

OpenAPI-MCP is a proxy server that bridges AI agents and external APIs by translating OpenAPI specifications into standardized Model Context Protocol (MCP) tools, simplifying integration and reducing development complexity.

How to use OpenAPI-MCP?

To use OpenAPI-MCP, clone the repository, install the required packages, configure the environment variables, and run the server using the provided commands.

Key features of OpenAPI-MCP?

  • Dynamic tool generation from OpenAPI endpoints.
  • Supports multiple transport methods including stdio and Server-Sent Events (SSE).
  • OAuth2 support for secure interactions.
  • Dry run mode for safe API simulations.
  • JSON-RPC 2.0 compliance for robust communication.
  • Integration with popular AI orchestrators like Cursor and Windsurf.

Use cases of OpenAPI-MCP?

  1. Seamless integration of AI agents with various APIs.
  2. Rapid development of applications requiring API interactions.
  3. Simplifying the process of creating custom API wrappers.

FAQ from OpenAPI-MCP?

  • What is the purpose of OpenAPI-MCP?

It simplifies the integration of AI agents with external APIs by standardizing communication through MCP.

  • Is OpenAPI-MCP easy to set up?

Yes! It requires cloning the repository and configuring a few environment variables.

  • Can OpenAPI-MCP handle multiple APIs?

Yes! It can dynamically generate tools for multiple OpenAPI specifications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gujord
Star
5
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago