To attach an MCP server to each of hundreds of Naver Cloud Platform services, every service team had to implement MCP from scratch. We built an MCP Generator to solve this — automatically generating MCP server code from OpenAPI specs.
Then Claude's MCP Builder Skills arrived. Suddenly, anyone could build an MCP server through a few conversations with Claude. The value of the generator we had built disappeared overnight.
We had to change direction. And the question changed with it — from "how do we make building MCP servers easier?" to "how do we operate hundreds of them?"
That's how MCP Gateway was born. It aggregates multiple MCP servers behind a single HTTP endpoint, so users can connect every cloud service tool to their AI agent with just one URL and one API key.
This talk is structured in two parts:
Part 1 — The Journey: The process of figuring out how to provide good MCP servers for hundreds of cloud services — what problems we found, what we tried, and how the arrival of MCP Builder Skills became the turning point.
Part 2 — MCP Gateway: An introduction and demo of what problems it solves today, and a look at what we're building next.
