MCP Dev Summit Bengaluru 2026

MCP reached infrastructure currency in 13 weeks. CNCF took 13 months. That compression is the problem. The shared plumbing every production MCP deployment now reinvents, because no neutral open implementation exists yet, has to be built in months instead of years.

This talk maps five missing layers of the MCP ecosystem and what each needs before the protocol scales two more orders of magnitude.

1. Discovery federation. One registry lookup does not survive public, private, and vendor registries coexisting.
2. Workload identity for servers. Not user OAuth. Who is this server, who signed it, what is it allowed to do?
3. Observability backbone. OpenTelemetry semantic conventions for MCP are still draft, so every gateway ships its own trace format.
4. Health and reputation signals. When seventeen servers are named github-mcp, which one should an agent trust?
5. Metering and cost attribution. Boring, load bearing, absent from the spec.

For each layer: what exists today, where it breaks at scale, what a minimum viable open implementation needs. Attendees leave with a concrete map of which gaps are urgent, which are deferrable, and which are already being filled.

For fifty years, software has been built around one consumer: the human user. Every API pattern, every UX principle, every interaction model has assumed a person on the other end. In the last eighteen months, that assumption broke.

The consumer of software is increasingly not a person — it's a language model, reasoning about systems on our behalf. The Model Context Protocol is the first widely adopted standard for this new world, but MCP is just the skeleton. The real work — designing for the machine experience — is a discipline we are inventing in real time.

In this opening keynote, Sam Partee (CTO and Co-Founder of Arcade.dev) frames where we are, what's at stake, and why the builders in this room have a once-in-a-generation opportunity to define how software will be designed, secured, and consumed for the next decade.

What does it take to build agentic AI systems that are scalable, affordable, and trustworthy for India? This keynote explores the emerging AI stack powering next-generation healthcare and public service workflows from frontier and small models to interoperable MCP architectures and DPI integration.

Speakers from the Gates Foundation, Eka Care, and EkStep Foundation discuss the technical and governance choices that will shape AI deployment across India and other emerging markets.

Local MCP prototyping is magic on a laptop, but scaling to production often triggers "Agentic Sprawl." To handle complex agent loops at scale, enterprises need a centralized architecture for integration, identity, and governance. This keynote explores Google Cloud’s full-stack vision for internet-scale agents. We will unpack the shift toward stateless MCP transports to solve multi-round-trip routing bottlenecks, show how Apigee converts legacy APIs into zero-code MCP skills, and highlight how developer tools like Antigravity and the Agent Development Kit (ADK) push the boundaries of AI from the cloud to the device.

Goose is an open-source AI agent that can be extended through integrations, tools, and community-driven projects. In this talk, I'll share my journey working with Goose, explore how its capabilities can be extended through community-driven projects, highlight examples from the Goose ecosystem, and discuss the development of GooseBot as one approach to bringing AI agents closer to developer communities. Along the way, I'll cover lessons learned from building in the open and why extensibility is key to the future of open-source AI agents.

The Model Context Protocol (MCP) is now an LF project, and that's fantastic news for the open source ecosystem. Last year MCP servers went mainstream fast, linking up AI models with apps, data and systems. Whether you are managing it or not, hundreds of people are already using MCPs within your company. Unfortunately, many IT teams are discovering this adoption, not planning it.

This talk provides a quick intro to the MCP ecosystem, and presents a four-stage maturity model for MCP adoption, from tracking shadow MCP development to secure, enterprise-wide deployment. You'll learn where your organization actually is (most are Stage 1 or early Stage 2), what infrastructure you need for each stage, and how to build the process and policies to turn MCP from a risk into an enabling technology.

This model is based on patterns from real deployments and hundreds of engagements with engineers dealing with this right now. I'll touch on MCP development, security, management, operations and how to get these incredibly useful tools into the hands of more and more users within your company.