From f7dab945cd67211c00a3e78615e8943ee1e913ac Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Sun, 30 Mar 2025 04:41:14 -0700 Subject: [PATCH] Update README.md --- README.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2aad51c..ebec69d 100644 --- a/README.md +++ b/README.md @@ -46,17 +46,23 @@ Reference implementations provided in this repository demonstrate common use-cas ## 🔌 Bridge to MCP (Optional) -For your convenience, we also provide a simple, secure MCP-to-OpenAPI proxy server. This enables tool providers who initially implemented MCP servers to expose them effortlessly as standard OpenAPI-compatible APIs, ensuring existing MCP servers and resources remain accessible without additional hassle. +For the easiest way to expose your MCP tools as OpenAPI-compatible APIs, we recommend using [mcpo](https://github.com/open-webui/mcpo). This enables tool providers who initially implemented MCP servers to expose them effortlessly as standard OpenAPI-compatible APIs, ensuring existing MCP servers and resources remain accessible without additional hassle. -**Example usage:** +**Quick Usage:** +```bash +uvx mcpo --port 8000 -- uvx mcp-server-time --local-timezone=America/New_York +``` +Alternatively, we also provide a simple Python-based proxy server: + +**Example:** ```bash cd servers/mcp-proxy pip install -r requirements.txt python main.py --host 0.0.0.0 --port 8000 -- uvx mcp-server-time --local-timezone=America/New_York ``` -This can simplify your migration or integration path, avoiding headaches typically associated with MCP's transport and security complexities. +Both methods help bridge existing MCP servers with OpenAPI clients, removing transport and security complexities during integration or migration. ## 📜 License