Untitled topic

As the MCP ecosystem continues to grow, more projects and B2B services are starting to adopt MCP.

When MCP is truly applied in production environments, adapting and integrating existing API services will inevitably become a challenge — often requiring significant engineering and system investments.

That’s why I believe there is a real need for an “Nginx-like” reverse proxy at the MCP layer — a tool that enables individuals and businesses to quickly connect their existing APIs into the MCP ecosystem at low cost, allowing them to validate ideas and markets without heavy upfront refactoring.

Currently, Higress is the major gateway solution supporting MCP, and it demonstrates strong technical advantages in large-scale scenarios. However, in terms of access cost, documentation maturity, and development flexibility, it may pose a higher barrier for some projects — especially when second development is needed, given the complexity of the Istio/Envoy/Wasm stack.

Based on this background, I built and open-sourced MCP Gateway — a lightweight, platform-neutral, and low-overhead MCP gateway that can be quickly deployed on local machines, standalone servers, or Kubernetes. Through simple configuration, you can easily transform existing API services into MCP servers.

Today, MCP Gateway is officially launched on Product Hunt! If you find it valuable, I’d greatly appreciate your upvote!

The future of this market is still uncertain, but I truly believe building a tool that fills this gap and lowers the adoption barrier is something meaningful. You’re warmly welcome to try it out — and I’d love to hear your feedback and suggestions!

GitHub: https://github.com/mcp-ecosystem/mcp-gateway Product Hunt: https://www.producthunt.com/posts/mcp-gateway