OpenAPI MCP Server

Created By
prompteus-aia year ago
An MCP server proxy that exposes OpenAPI-based APIs.
Overview

What is OpenAPI MCP Server?

OpenAPI MCP Server is a Cloudflare Workers-based service that dynamically creates an MCP server from any OpenAPI schema definition endpoint, enabling seamless integration with various tools.

How to use OpenAPI MCP Server?

To use the OpenAPI MCP Server, install the dependencies with npm install, run the service locally using npm run dev, and access it at http://localhost:8787. Alternatively, use the hosted version at https://bridge.openapitomcp.com.

Key features of OpenAPI MCP Server?

  • Dynamic creation of MCP servers from OpenAPI schemas
  • Stateless proxy between MCP clients and OpenAPI-documented APIs
  • Easy integration with tools like Prompteus, Claude, and Cursor
  • Web interface for automatic configuration payload generation

Use cases of OpenAPI MCP Server?

  1. Integrating with APIs like PetStore using OpenAPI schemas.
  2. Creating complex workflows in Prompteus that leverage MCP servers.
  3. Facilitating API interactions through various tools with a consistent interface.

FAQ from OpenAPI MCP Server?

  • Can I use OpenAPI MCP Server with any OpenAPI schema?

Yes! It supports any OpenAPI schema definition.

  • Is there a hosted version available?

Yes! A free hosted version is available at https://bridge.openapitomcp.com.

  • How do I configure the MCP server?

Configuration is done by passing a base64url-encoded JSON object in the URL.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
prompteus-ai
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago