MCP OpenAPI

Created By
electrocucarachaa year ago
MCP Generator using OpenAPI spec
Overview

What is MCP OpenAPI?

MCP OpenAPI is a tool designed to accelerate the adoption of the MCP protocol by automating the generation of server components from OpenAPI specifications.

How to use MCP OpenAPI?

To use MCP OpenAPI, simply provide an OpenAPI specification, and the tool will dynamically generate the corresponding MCP-compatible server code and tools.

Key features of MCP OpenAPI?

  • Parses OpenAPI specifications to generate server components.
  • Automates the creation of MCP-compatible server code.
  • Streamlines integration and deployment processes.

Use cases of MCP OpenAPI?

  1. Deploying as a sidecar alongside existing services for seamless MCP support.
  2. Reducing manual server implementation efforts in modern service architectures.

FAQ from MCP OpenAPI?

  • What is the main purpose of MCP OpenAPI?

To simplify server generation and promote faster adoption of the MCP protocol.

  • Is MCP OpenAPI easy to integrate with existing services?

Yes! It is designed to work alongside existing services without requiring extensive changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
electrocucaracha
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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