<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protocol on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/protocol/</link><description>Recent content in Protocol on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 Mar 2026 14:00:00 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/protocol/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Protocol Explained: The Universal Standard for AI Tools</title><link>http://www.heyuan110.com/posts/ai/2026-02-28-mcp-protocol-explained/</link><pubDate>Mon, 02 Mar 2026 14:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-02-28-mcp-protocol-explained/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-02-28-mcp-protocol-explained/cover.webp"
 alt="MCP Protocol architecture and ecosystem explained for 2026"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;Every AI coding tool needs to connect to external services — databases, APIs, cloud platforms, project management tools. Before MCP, each connection required custom integration code. Build it for Claude Code? Rebuild it for Cursor. Rebuild it again for Copilot.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Model Context Protocol (MCP)&lt;/strong&gt; solves this with a universal standard: build one integration, and it works with every AI tool that supports MCP.&lt;/p&gt;</description></item></channel></rss>