MCP Dev Summit Bengaluru 2026

**Space Limited - First Come, First Served.  Please bring a fully charged laptop to the workshop**

A single coding agent is useful. Real engineering work spans multiple machines and repos, and coordination breaks the moment two agents cooperate. What does it take to build an MCP server that manages a fleet lifecycle from one conversation and enforces quality on output?

This workshop uses apra-fleet (Apache 2.0) as a worked example of pushing MCP into distributed agent coordination, with tool schemas encoding a doer-reviewer pattern and review gates.

Part 1, Server architecture: Transport selection (stdio vs HTTP) for long-running fleets, a strategy pattern abstracting SSH and local execution behind one tool surface, provider adapters for Claude, Gemini, and Codex, and git-backed session state for checkpointing.

Part 2, Fleet in action: A live sprint. Fleet registration, credential provisioning, task decomposition, doer-reviewer assignment, and parallel execution through review gates, via MCP tool calls.

Part 3, Failure modes: Agent crashes, SSH drops, reviewer rejections. Real failures triggered on stage, recovered from exact breakpoints using git state.

You'll leave with concrete patterns for building MCP servers that coordinate distributed agents, not just expose tools.

**Space Limited - First Come, First Served.  Please bring a fully charged laptop to the workshop**

Scaling autonomous agents across multi-cloud infrastructure is currently a mess of proprietary SDKs and brittle "glue code." This workshop provides a technical build-path to standardize operations using orchestration frameworks (like OpenClaw) and the Model Context Protocol (MCP) as a provider-agnostic abstraction layer. We will move beyond theoretical planning to build a functional "Agentic SRE" control plane that decouples reasoning from execution across AWS and GCP.

Implementation Workflow:

- Initialization: Bootstrapping the pre-configured DevContainer and linking the orchestration engine to the local MCP server environment to establish the communication backbone.

- Resource Abstraction: Developing stateless MCP Resources and Tools to discover VPC and compute metadata across disparate cloud providers, replacing $O(N)$ proprietary dependencies with an $O(1)$ protocol interface.

- Identity Implementation: Configuring Workload Identity Federation (OIDC) to securely propagate agent context.

- Guardrail Integration: Coding a protocol-level interceptor

- Closing & Validation: Running a live "Drift-to-Remediation" loop where the agent identifies a security anomaly.

**Space Limited - First Come, First Served.  Please bring a fully charged laptop to the workshop**

Enterprise adoption of the Model Context Protocol is accelerating — but the path from "MCP works on my laptop" to "MCP running securely across our organization" is windy and challenging.
Building MCP servers isn't particularly hard. The real challenges are OAuth, identity sprawl, and the governance requirements your security team will eventually land on your desk.
MCP servers should focus on tools, resources, and prompts — not rebuilding OAuth infrastructure from scratch every time. A dedicated identity and governance control plane absorbs that complexity once, rather than forcing every server to solve it independently.
In this workshop, we will:
1. Demonstrate how to integrated MCP servers with identity management tools
2. Show how to tailor MCP authorization by groups and policies.
3. Work through real governance scenarios by filtering MCP calls for PII or code injection.
4. Demonstrate how MCP traffic can be captured via an MCP gateway and used for compliance, monitoring and observability.

You'll leave with a clear picture of the architectural decisions ahead of you, and a better sense of what your security team is going to ask for before they sign off on scaling MCP adoption.