--- title: "Discussion on \"A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless\" | Hashnode" description: "Discussion on \"A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless\". Key insights from AWS Community Day Bengaluru | July 11, 2026" url: "https://hashnode.com/posts/a2a-mcp-building-self-orchestrating-multi-agent-workflows-on-aws-serverless/6aba458389b9459d40d5b494" --- [Feed](https://hashnode.com/feed) / Discussion # [A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless](https://devopstour.hashnode.dev/a2a-mcp-building-self-orchestrating-multi-agent-workflows-on-aws-serverless?utm_source=hashnode&utm_medium=feed) Key insights from AWS Community Day Bengaluru | July 11, 2026 Sep 28 ยท 8 min read ยท devopstour.hashnode.dev Read the article - [#aws](https://hashnode.com/tag/aws) - [#amazon-web-services](https://hashnode.com/tag/amazon-web-services) - [#ai-agents](https://hashnode.com/tag/ai-agents) - [#gen-ai](https://hashnode.com/tag/gen-ai) - [#serverless](https://hashnode.com/tag/serverless) - [#mcp](https://hashnode.com/tag/mcp) - [#model-context-protocol](https://hashnode.com/tag/model-context-protocol) - [#aws-community-day-bengaluru-2026](https://hashnode.com/tag/aws-community-day-bengaluru-2026) - [#acdblr26](https://hashnode.com/tag/acdblr26) - [#llm](https://hashnode.com/tag/llm) - [#cloud-computing](https://hashnode.com/tag/cloud-computing) - [#ai](https://hashnode.com/tag/ai) ## Written by [N Chandra Prakash Reddy](https://hashnode.com/@ChandraPrakash1996) @ChandraPrakash1996 ยท India [View profile](https://hashnode.com/@ChandraPrakash1996) AWS Community Builder | Cloud | DevOps Engineer | Blogger \-> I'm an enthusiastic DevOps professional with over 3+ years of hands-on expertise in cloud infrastructure management and orchestrating the deployment of applications which are ready for production. -> Excellent problem-solving skills and a proactive learner, staying updated with the latest trends in DevOps and Cloud Computing. ๐†๐ž๐ญ ๐ข๐ง ๐“๐จ๐ฎ๐œ๐ก -> ๐‚๐จ๐ง๐ง๐ž๐œ๐ญ ๐จ๐ง ๐‹๐ข๐ง๐ค๐ž๐๐ข๐ง : If you're interested in engaging in technical discussions or connecting professionally, please feel free to connect with me on LinkedIn. -> ๐„๐ฆ๐š๐ข๐ฅ : ncpr.0912@gmail.com ## Responses 1 Markdown supported ยท โŒ˜โ†ต to post [Kartik N V J K](https://hashnode.com/@kartik-nvj) [Sep 28](https://hashnode.com/posts/a2a-mcp-building-self-orchestrating-multi-agent-workflows-on-aws-serverless/6aba458389b9459d40d5b494/comment/6ababbee1ca73c08cbffcc5c) The 5 tools at 95% versus 30 tools at 48% number is the one I keep coming back to, because it reframes tool overload as a measurable accuracy cliff rather than a vague smell. Splitting into special-purpose agents helps, but it moves the risk to the handoff, which is where I see most multi-agent systems actually break. I wrote up how I vet MCP servers before trusting them in an agent, the same trust concern from the tool side: [kartiknvjk.hashnode.dev/how-i-evaluate-mcp-serverโ€ฆ](https://kartiknvjk.hashnode.dev/how-i-evaluate-mcp-servers-for-security-before-i-trust-them) . Did accuracy recover once each sub-agent was back down to a handful of tools?