MCP Dev Summit North America

MCPs unlock agent data access, but that's only the first step towards building agents that can work autonomously. How do we build a complete system where multiple agents work together, maintain state across sessions, and the whole thing runs reliably every day.

I use agents that work with 10+ connections daily for both personal and work use cases: health MCPs/APIs (Strava, Apple Health), productivity tools (Calendar, Linear), business systems (Attio CRM, email), and developer tools (GitHub). This talk shares effective architectural patterns that emerged from actually using this system.

We'll cover MCP composition (Virtual MCPs) and how to orchestrate multiple agents with memory. We show how state management using Git as agent memory is effective, as it provides versioning and rollback. We treat CLAUDE.md files as behavioral memory in the same system. Finally, we cover security concerns and best practices to manage agents that have access to sensitive and/or untrusted data.