Official description3 sourcesMCP servers3d ago

criteo/openapi-to-mcp

An MCP server for your API

View on GitHub ↗Direct link · no redirect page

Source: collected from the abordage/awesome-mcp list · type: MCP server
Harvest history: first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
Score: score 303 · 3 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

first catalogued 2026-10-14；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

openapi-to-mcp

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

Use your OpenAPI specification to expose your API's endpoints as strongly typed tools.
Basic example for https://petstore3.swagger.io/ 🎉
More complex example, using Github's API:
This example use the bearer token auth (with a Github Personal Access Token) and force the tool naming strategy to "verb and path", as Github's operation ids are not valid tool names.
Install
As a Nuget tool: openapi-to-mcp
Or download the executables from the releases
Usage
OpenAPI support
- Currently, OpenAPI 2.0 and 3.0 are supported.
- 3.1 is not (at least not until microsoft/OpenAPI.NET supports it)
- Specifications can be JSON/YAML and local (file) or remote (URL)
- Only local $refs are supported
OpenAPI custom extensions
A set of custom extensions is available to customize how your API should be exposed:
- info.x-mcp-instructions (string): Textual instructions exposed by the MCP server during the initialize handshake
- operation.x-mcp-tool-name (string): Custom tool name
- operation.x-mcp-tool-description (string): Custom tool description
- operation.x-mcp-tool-enabled (boolean): Enabled/disabled a specific operation (enabled by default)
MCP features
Only STDIO transport is currently supported.
Tools
Operations ("endpoints") from your OpenAPI specification are translated to MCP tools
- All path/query/JSON body parameters are exposed (using their JSON schema)
- Response is returned as-is
- By default, the tool name is computed using first the operation.x-mcp-tool-name extension, then the operation.operationId and then {httpMethod}_{escaped_path}
- The tool naming strategy can be defined via the --tool-naming-strategy option.
- ⚠️Tools are discarded if their name don't match ^[a-zA-Z0-9_-]{1,64}$
- Tools description are extracted as follows: operation.x-mcp-tool-description ?? operation.description ?? path.description
Tool call and host
When a tool is called, the MCP server will call the underlying endpoint. To determine which host to call a combination of parameters are used:
- the --host-override option
- your specification first server's URL if it's an absolute URL
- the host of the remote OpenAPI provided
- otherwise, an error is thrown
For example running openapi-to-mcp https://petstore3.swagger.io/api/v3/openapi.json:
- https://petstore3.swagger.io/api/v3/openapi.json defines a server, but its URL is relative (/api/v3)