MCP Dev Summit Seoul 2026

Most MCP systems today are static at runtime. We define tools, expose schemas and rely on prompts to guide behavior, then hope the system remains reliable after deployment.

In practice, MCP-based systems drift. Agents repeatedly misuse tools, call inefficient sequences or fail in predictable ways. Tool descriptions become outdated. Context grows noisy. Human operators step in to correct outcomes, but those corrections are rarely captured or reused. MCP standardizes how agents connect to tools, but it does not define how systems improve over time.

I would like to explore how to build MCP systems that go beyond execution by introducing feedback loops on top of the protocol. By combining tool call history and observability, we can build systems that identify their own weaknesses and suggest improvements safely.

The session will cover practical patterns:
- Detecting repeated tool misuse and failure patterns
- Learning from retries, fallbacks, and human corrections
- Identifying redundant or low-value tool chains
- Designing safe feedback loops with audit logs, versioning, rollback and human approval