<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Antonio Cortés (DrZippie)</title><link>https://antoniocortes.com/tags/architecture/</link><description>Recent content in Architecture on Antonio Cortés (DrZippie)</description><generator>Hugo</generator><language>es-es</language><lastBuildDate>Sun, 01 Feb 2026 21:46:02 +0100</lastBuildDate><atom:link href="https://antoniocortes.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>A2A vs MCP: Tools or Agents? The difference that will change how we build AI systems</title><link>https://antoniocortes.com/en/post/2025/07/a2a_vs_mcp_herramientas_agentes_09_julio_2025/</link><pubDate>Wed, 09 Jul 2025 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/post/2025/07/a2a_vs_mcp_herramientas_agentes_09_julio_2025/</guid><description>&lt;h2 id="two-protocols-two-philosophies"&gt;Two protocols, two philosophies&lt;/h2&gt;
&lt;p&gt;In recent months, two protocols have emerged that will change how we build AI systems: &lt;strong&gt;&lt;a href="https://a2aprotocol.ai/"&gt;Agent2Agent Protocol (A2A)&lt;/a&gt;&lt;/strong&gt; from Google and &lt;strong&gt;&lt;a href="https://modelcontextprotocol.io/"&gt;Model Context Protocol (MCP)&lt;/a&gt;&lt;/strong&gt; from Anthropic. But here&amp;rsquo;s the thing: &lt;strong&gt;they don&amp;rsquo;t compete with each other&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In fact, after analyzing both for weeks, I&amp;rsquo;ve realized that understanding the difference between A2A and MCP is crucial for anyone building AI systems beyond simple chatbots.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The key lies in one question&lt;/strong&gt;: Are you connecting an AI with tools, or are you coordinating multiple intelligences?&lt;/p&gt;</description></item></channel></rss>