Any Openapi MCP Server

Any Openapi MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Eventually I came down to this solution: - It uses in-memory semantic search to find relevant Api endpoints by natural language (such as list products) - It returns the complete end-point docs (as I designed it to store one endpoint as one.

What you get

• 🧠 Use remote openapi json file as source, no local file system access, no updating required for API changes
• 🔍 Semantic search using optimized MiniLM-L3 model (43MB vs original 90MB)
• 🚀 FastAPI-based server with async support
• 🧠 Endpoint based chunking OpenAPI specs (handles 100KB+ documents), no loss of endpoint context
• ⚡ In-memory FAISS vector search for instant endpoint discovery

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 2 environment variables: OPENAPI_JSON_DOCS_URL, API_REQUEST_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the any openapi mcp server does with a few real requests.

Choosing this one

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by baryhuang; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.