MCP Dev Summit Seoul 2026

As teams adopt MCP, a common anti-pattern appears: expose an entire API surface as tools and hope the agent figures it out. In practice this leads to confusion, brittle behavior, and security headaches.

In this talk, I’ll walk through a practical architecture for taming that complexity using MCP flavors and a Public MCP gateway. We’ll start from the real constraints: large APIs, multiple products, and agents that need a bit of more focus & from there:

- design flavors as curated tool bundles on top of existing OpenAPI contracts;
- expose them via a gateway (/mcp vs /{flavorId}/mcp) while handling auth and routing cleanly;
- and plug these flavors into agents in editors or chat environments.

I’ll also cover how to evaluate and debug flavors using datasets and traces so they’re treated like product surfaces with their own quality bar, not opaque black boxes. Finally, I’ll share lessons learned ramping from a mostly frontend/“traditional” engineering background into MCP and agentic infrastructure work: what worked, what didn’t, and what I’d do differently.