MCP Dev Summit Seoul 2026

In this workshop, you'll build a complete MCP-powered agentic system in Java from scratch.

We'll start by building an MCP server. You'll see how familiar the programming model is: annotate a method with @Tool, configure a transport, and your service speaks MCP. We'll connect it to a real-world API so the tools do something useful, not just "hello world."

Next, we'll build an AI agent that discovers and calls those MCP tools through natural language. You'll see how dependency injection and type safety make multi-tool composition clean and testable, and how hot reload lets you iterate on agent behavior in seconds.

Finally, we'll compose multiple agents into a workflow, including a supervisor agent that autonomously routes tasks to specialist agents, each with their own tools and MCP connections.

All materials are open source and based on a battle-tested workshop delivered to developer audiences worldwide. Attendees leave with running code and reusable patterns they can apply immediately.

When people talk about MCP, they think of a server protocol for desktop AI — Claude Desktop reading the filesystem, Cursor calling git, MCP servers humming on cloud infrastructure. But there's a whole other world that rarely shows up in the conversation: phones, smart watches, glasses, cars, robots, embedded edge devices. They all have mature SDKs, many can run small AI models locally, and almost none have an agentic tool layer to speak of. The natural question is: why isn't MCP there yet?
Turns out it can be — and is starting to be. This talk is about MCP in the mobile and broader smart-device world: what scenarios already work today, what's just landing, and what becomes possible when a device is no longer just a client to a cloud agent but a peer in a multi-device agentic system. We'll cover phones that host their own MCP servers exposing device capabilities, phones running an entire agent loop on-device with no network, system-level integrations Apple and Google are bringing through App Intents and AICore, and hybrid setups where local and cloud servers share one tool registry — then extend the picture beyond phones to glasses, cars, watches, and embedded edge