higress-group/openapi-to-mcpserver

OpenAPI document to a Higress MCP server config

Before you install: a copy-paste command is available · no license recorded · link reachable

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site

Install & config

Copy the command above
Paste it as one entry under mcpServers in claude_desktop_config.json — local servers take command + args (example: clients)
Restart your client

Install command from the repository

go install github.com/higress-group/openapi-to-mcpserver/cmd/openapi-to-mcp@latest

Parsed from the README we fetched on 2026-11-05; we have not executed it.

This is the install method the repository states, not an MCP client config, so no JSON is generated.

Key names differ by client: Clients & CLI

Source: collected from the abordage/awesome-mcp list · type: MCP server
Harvest history: first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score: score 1,003 · 10 sources · mcp
Install: go install github.com/higress-group/openapi-to-mcpserver/cmd/openapi-to-mcp@latest

FAQ (answers come from our records)

How do I install it?

The repository provides this install command: go install github.com/higress-group/openapi-to-mcpserver/cmd/openapi-to-mcp@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.

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-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# OpenAPI to MCP Server

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

A tool to convert OpenAPI specifications to MCP (Model Context Protocol) server configurations.
## Installation
bash
go install github.com/higress-group/openapi-to-mcpserver/cmd/openapi-to-mcp@latest
## Usage
bash
openapi-to-mcp --input path/to/openapi.json --output path/to/mcp-server.yaml
### Options
--input: Path to the OpenAPI specification file (JSON or YAML) (required)
--output: Path to the output MCP configuration file (YAML) (required)
--server-name: Name of the MCP server (default: "openapi-server")
--tool-prefix: Prefix for tool names (default: "")
--format: Output format (yaml or json) (default: "yaml")
--validate: Validate the OpenAPI specification (default: false)
--template: Path to a template file to patch the output (default: "")
## Example
bash
openapi-to-mcp --input petstore.json --output petstore-mcp.yaml --server-name petstore
### Converting OpenAPI to Higress REST-to-MCP Configuration
This tool can be used to convert an OpenAPI specification to a Higress REST-to-MCP configuration. Here's a complete example:
1. Start with an OpenAPI specification (petstore.json):
json
"openapi": "3.0.0",
"info": {
"version": "1.0.0",
"title": "Swagger Petstore",
"description": "A sample API that uses a petstore as an example to demonstrate features in the OpenAPI 3.0 specification"
},
"servers": [
"url": "http://petstore.swagger.io/v1"
],
"paths": {
"/pets": {
"get": {
"summary": "List all pets",
"operationId": "listPets",
"parameters": [
"name": "limit",
"in": "query",
"description": "How many items to return at one time (max 100)",
"required": false,
"schema": {
"type": "integer",
"format": "int32"
],
"responses": {
"200": {
"description": "A paged array of pets",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"pets": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "integer",
"description": "Unique identifier for the pet"
},
"name": {
"type": "string",
"description": "Name of the pet"
},
"tag": {
"type": "string",
"description": "Tag of the pet"
},
"nextPage": {
"type": "string",
"description": "URL to get the next page of pets"
},
"post": {
"summary": "Create a pet",
"operationId": "createPets",
"requestBody": {
"description": "Pet to add to the store",
"required": true,
"content": {
"application/json": {
"schema": {
"type": "object",
"required": ["name"],
"properties": {
"name": {
"type": "string",
"description": "Name of the pet"
},
"tag": {
"type": "string",
"description": "Tag of the pet"
},
"responses": {
"201": {
"description": "Null response"
},
"/pets/{petId}": {
"get": {
"summary": "Info for a specific pet",
"operationId": "showPetById",
"parameters": [
"name": "petId",
"in": "path",
"required": true,
"description": "The id of the pet to retrieve",
"schema": {
"type": "string"
],
"responses": {
"200": {
"description": "Expected response to a valid request",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"id": {
"type": "integer",
"description": "Unique identifier for the pet"
},
"name": {
"type": "string",
"description": "Name of the pet"
},
"tag": {
"type": "string",
"description": "Tag of the pet"
2. Convert it to a Higress REST-to-MCP configuration:
bash
openapi-to-mcp --input petstore.json --output petstore-mcp.yaml --server-name petstore

Listed badge (optional)

Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.

[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/higress-group-openapi-to-mcpserver/)

Source: awesome · https://github.com/higress-group/openapi-to-mcpserver
Browse by field: MCP servers
Listed by: 10 independent sources
added: today

More like this

glenngillen/mcpmcp-serverMCP server VeriTeknik/pluggedin-mcp-proxyMCP server nwiizo/tfmcpMCP server WayStation-ai/mcpMCP server

All 6,229 →

Filed under

MCP servers6,229 entries MCP server6,545 Curated list pick6,618

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index