OpenAPI MCP Server

Created By
3loca year ago
This is a skeleton project that you can use as a starting point for building your own MCP server. The example addition function demonstrates how to implement handlers across all three protocols.
Overview

What is OpenAPI MCP Server?

OpenAPI MCP Server is a skeleton project designed to help developers build their own MCP (Multi-Channel Protocol) servers. It provides a foundational structure and an example addition function to demonstrate how to implement handlers across various protocols.

How to use OpenAPI MCP Server?

To use the OpenAPI MCP Server, you can build and run it using Docker or Docker Compose. You can choose to run it in different modes: standard I/O, Server-Sent Events (SSE), or OpenAPI/REST endpoints.

Key features of OpenAPI MCP Server?

  • Supports multiple communication protocols: stdio, SSE, and OpenAPI/REST.
  • Easy to configure using an mcp.json file.
  • Example implementation of an addition function.

Use cases of OpenAPI MCP Server?

  1. Building custom MCP servers for various applications.
  2. Implementing real-time data streaming using SSE.
  3. Creating RESTful APIs with OpenAPI specifications.

FAQ from OpenAPI MCP Server?

  • What protocols does the OpenAPI MCP Server support?

It supports standard I/O, Server-Sent Events, and OpenAPI/REST endpoints.

  • How can I run the server?

You can run the server using Docker or Docker Compose, specifying the desired mode through the MODE environment variable.

  • Is there an example configuration available?

Yes, the project includes an example mcp.json configuration file for reference.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

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

6 hours ago