OPENAPI Specifications => MCP (Model Context Protocol) Tools

Created By
2013xilea year ago
OpenAPI specifications => MCP (Model Context Protocol) tools
Overview

what is openapi2mcptools?

openapi2mcptools is a utility library designed for converting OpenAPI specifications into tools compatible with the Model Context Protocol (MCP), streamlining the development of MCP servers based on OpenAPI specifications.

how to use openapi2mcptools?

To use openapi2mcptools, import the Converter class from the library, load your OpenAPI specifications, and define your MCP server to handle requests using the converted tools.

key features of openapi2mcptools?

  • Converts OpenAPI specifications to MCP-compatible tools.
  • Simplifies the creation of MCP servers based on OpenAPI.
  • Customizable HTTP client options for flexibility in requests.

use cases of openapi2mcptools?

  1. Rapid development of MCP servers using existing OpenAPI documentation.
  2. Integration of MCP tools in applications leveraging OpenAPI frameworks.
  3. Automating the translation between OpenAPI specs and MCP functionalities.

FAQ from openapi2mcptools?

  • Is openapi2mcptools suitable for all types of APIs?

Yes, it effectively converts a wide range of OpenAPI specifications into MCP tools.

  • Can I customize the HTTP client used in the library?

Yes, the library allows you to set custom HTTP client configurations such as base URL and headers.

  • What programming language is openapi2mcptools compatible with?

The library is built for TypeScript but can easily be integrated into JavaScript environments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
2013xile
Star
-
Language
-
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