OAS-MCP

Created By
nonchan7720a year ago
openapi to mcp server
Overview

What is OAS-MCP?

OAS-MCP is a tool that automatically generates a Model Context Protocol (MCP) server from OpenAPI specifications (YAML/JSON). It is a Go application that allows each OpenAPI endpoint to be utilized as an MCP tool.

How to use OAS-MCP?

To use OAS-MCP, clone the repository, install the dependencies, and run the command to generate client code from your OpenAPI specification. You can also use the go:generate command for code generation.

Key features of OAS-MCP?

  • Automatic generation of Go client code from OpenAPI specifications.
  • Building MCP servers using the generated client code.
  • Providing each API endpoint as an MCP tool.
  • Real-time communication utilizing Server-Sent Events (SSE).

Use cases of OAS-MCP?

  1. Generating client code for RESTful APIs.
  2. Building real-time applications using MCP servers.
  3. Simplifying the integration of OpenAPI specifications into Go applications.

FAQ from OAS-MCP?

  • What are the system requirements for OAS-MCP?

OAS-MCP requires Go version 1.24 or higher.

  • Is OAS-MCP open source?

Yes! OAS-MCP is provided as open-source software under the MIT license.

  • Where can I find the documentation?

Documentation can be found in the repository on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nonchan7720
Star
0
Language
Go
License
MIT 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)

5 hours ago