MCP Dev Summit Seoul 2026

Six months ago, building a voice AI agent on our platform meant clicking through a UI. This meant editing prompts, dragging conversation flows, hooking up tools with no audit, no rollback, no review. To make the platform work better with MCP, we moved everything to a Git-backed harness. Each agent is now its own repo with skill folders and an agent.md capturing the agent's custom instructions and unique nuances, so when a customer points Cursor or Claude at it via MCP, the AI picks up that context before making any changes.

This talk covers:
(1) the org-change journey from clickops to version control
(2) the sandboxing model, how MCP safely exposes Git's branch model (dual read/write endpoints, tool-layer branch protection, SSO-derived org scoping)
(3) the two-stage CI on every PR, MCP-driven changes ride the same rails as human-authored ones, with simulations followed by automated evaluations
(4) the closed-loop flow that ties it all together, a user files an issue with a test scenario on an agent's page, the sandboxed AI makes the change, validates it, and submits a PR for review using MCP.