World's Fair 2025
Remote MCPs: What we learned from shipping — John Welsh, Anthropic
Overview
This talk discusses the challenges and solutions for implementing and scaling Message Communication Protocol (MCP) clients within a large organization. It highlights how the rapid evolution of AI models capable of tool calling led to integration chaos, with duplicated functionality and inconsistent interfaces across services. The solution proposed is to standardize on MCP for providing model context, treating it as a plumbing layer for integrations rather than a competitive differentiator.
Who should watch
- AI Engineers dealing with tool integration and custom endpoints.
- Product Managers looking to streamline AI-powered service development.
- Builders facing challenges with authentication, network connectivity, and auditing for LLM-backed services.
- Teams aiming to build integrations once and use them across multiple services.
Key takeaways
- The proliferation of AI models capable of tool calling has led to integration chaos, with many custom endpoints and duplicated functionality.
- MCP, particularly its message specification, provides a standardized way for models to communicate with external tools and context providers.
- Standardizing on MCP internally reduces engineering overhead, allowing teams to focus on core product features rather than integration plumbing.
- An MCP gateway can serve as a single point of entry for integrations, handling authentication, rate limiting, and observability centrally.
- The "pit of success" model, where the right way to do things is made the easiest, encourages adoption of standardized practices.
- MCP's flexibility allows for various transport mechanisms, including WebSockets, gRPC, or even email, as long as JSON streams are exchanged.
- Centralizing shared infrastructure concerns like external connectivity and authentication at a gateway layer frees up engineering resources.
- Adopting MCP provides future-proofing, as new protocol features are automatically available when internal packages are updated.
Notable quotes
*Being boring on stuff like this is good. It's not a competitive advantage to be really good at making Google Drive talk to your app.*
*The right thing to do, the easiest thing to do, then everyone in your org kind of falls into it.*
*MCP is really just JSON streams and how you pipe those streams around your infrastructure is a small implementation detail.*
Up next · MCP & tools
Watch next
The skeptic’s cut — what’s still broken before you bet the architecture.
MCP Is Not Good Yet — David Cramer, SentryUnofficial community note. Prefer the recording for nuance.