OpenAPI to MCP Server Converter

Created By
zxypro1a year ago
A tool for automatically converting OpenAPI specifications into Model Context Protocol (MCP) Server
Overview

What is OpenAPI to MCP Server Converter?

OpenAPI to MCP Server Converter is a tool designed to automatically convert OpenAPI specifications into Model Context Protocol (MCP) server instances, facilitating seamless integration and communication between different services.

How to use OpenAPI to MCP Server Converter?

To use the converter, first install the package via npm, then import it in your TypeScript project. Load your OpenAPI specification from a JSON file, create an instance of the converter, and run the server using the provided example code.

Key features of OpenAPI to MCP Server Converter?

  • 🚀 Automated Conversion: Automatically parses OpenAPI 3.0 specifications for easy conversion.
  • 🛠 Type Safety: Utilizes TypeScript for strong type validation, ensuring reliability.
  • 🔄 Request Proxy: Automatically manages parameter mapping for tool calls, simplifying integration.

Use cases of OpenAPI to MCP Server Converter?

  1. Converting RESTful API specifications into MCP server instances for better interoperability.
  2. Facilitating the development of microservices that require standardized communication protocols.
  3. Enhancing API documentation and testing workflows by providing a structured server environment.

FAQ from OpenAPI to MCP Server Converter?

  • What are the prerequisites for using this tool?

You need Node.js version 18 or higher and TypeScript version 5.x to run the converter.

  • Is there a way to test the converter?

Yes! You can run sample test cases using the command npm run test after installation.

  • What is the license for this project?

The project is licensed under the MIT License, allowing for open-source use and modification.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zxypro1
Star
1
Language
TypeScript
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)

2 days ago
Voyei

4 hours ago