From c15a0ef8eff3d11fbe70378ce6cd6c51f21aa127 Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Thu, 10 Apr 2025 18:30:13 -0700 Subject: [PATCH] Update README.md --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 91659e8..4d321e3 100644 --- a/README.md +++ b/README.md @@ -82,6 +82,27 @@ python main.py --host 0.0.0.0 --port 8000 -- uvx mcp-server-time --local-timezon Both methods help bridge existing MCP servers with OpenAPI clients, removing transport and security complexities during integration or migration. +## 🔃 Optional: Bridge OpenAPI → MCP Tool Server + +In addition to turning MCP tool servers into OpenAPI-compatible APIs (via mcpo or our proxy), it's also possible to go the other direction: expose your OpenAPI-compatible tool server as an MCP server. This makes it easy to integrate any OpenAPI tool into environments or agents that expect an MCP-compatible interface. + +Several community-maintained projects are available to help with this: + +- 🌉 openapi-mcp-server (by janwilmake) + ➤ https://github.com/janwilmake/openapi-mcp-server + Acts as a translator from any OpenAPI spec to an MCP tool, allowing for easy reuse of RESTful APIs within MCP-only frameworks. + +- 🔁 mcp-openapi-server (by ivo-toby) + ➤ https://github.com/ivo-toby/mcp-openapi-server + Another lightweight adapter that converts OpenAPI-described endpoints to usable MCP tool servers on the fly. + +With these bridges, you gain full interoperability in both directions: + +⟶ Run OpenAPI tools using existing MCP pipelines +⟶ Upgrade or replace MCP-native tools with more stable, secure, OpenAPI-based implementations + +This two-way bridge is a major step forward in simplifying tool architecture, empowering developers to choose the most efficient and future-proof infrastructure without compromising compatibility. + ## 📜 License Licensed under [MIT License](LICENSE).