From 08efbf0f57f805ab27671c9beff9d1fadedbd20b Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Thu, 10 Apr 2025 18:31:41 -0700 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d9ec78e..3c1bc0a 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ 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 +## 🔃 Bridge OpenAPI → MCP (Optional) 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.