MCP Dev Summit Seoul 2026

"MCP makes it easy to expose tools.
It does not make it easy to design systems."

At scale, that gap shows up as tool explosion, context limits, and unreliable execution.

As MCP servers grow, they accumulate large numbers of tools, fragmented abstractions, and stateful workflows, until agents struggle to discover, select, and reliably execute the right actions.

Attendees will leave with specific design patterns to make MCP servers more reliable, scalable, and easier for agents to use.

In building Appium MCP (github.com/appium/appium-mcp), we encountered this firsthand. Supporting real mobile automation required handling 100+ device actions, concurrent sessions across devices, and flaky UI interactions, quickly pushing naive MCP designs to their limits

In this talk, we demonstrate what breaks when MCP servers scale and how we changed our system

We evolved from loosely defined tools to an intent-driven interface, added elicitation for clearer execution, and integrated Appium Skills to extend capabilities.

These patterns enabled us to move beyond simple command execution toward composable, agent-driven automation, powering new projects like AppClaw - an extension to Appium MCP.