OpenAPI MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is OpenAPI MCP Server?

OpenAPI MCP Server is a tool that allows you to interact with any OpenAPI (v3.1) compliant API through Claude Desktop, acting as a proxy that converts OpenAPI endpoints into easy-to-use tools.

how to use OpenAPI MCP Server?

To use the OpenAPI MCP Server, configure Claude Desktop with the path to your OpenAPI specification and start interacting with the API through natural language commands.

key features of OpenAPI MCP Server?

  • Automatically converts OpenAPI endpoints into Claude tools for easy interaction
  • Supports file uploads for APIs that accept multipart/form-data
  • Handles API calls and responses automatically

use cases of OpenAPI MCP Server?

  1. Local testing of API endpoints through natural conversation.
  2. Quickly prototyping integrations with third-party APIs.
  3. Learning how to use APIs through interactive dialogue and examples.

FAQ from OpenAPI MCP Server?

  • What APIs does this server support?

The server supports any API that complies with the OpenAPI v3.1 specification.

  • Is there a file size limit for uploads?

The maximum file size is determined by the target API's specifications.

  • Can I use remote files for uploads?

No, the server currently supports only local files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours 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.

14 hours ago