<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LLM</title><link>https://blog.shuaizhang.cc/en-us/category/llm/</link><description>Posts gathered under this term.</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 24 Feb 2026 13:58:04 +0000</lastBuildDate><atom:link href="https://blog.shuaizhang.cc/en-us/category/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>Model Context Protocol Deep Dive (English Translation)</title><link>https://blog.shuaizhang.cc/en-us/posts/model-context-protocol-deep-dive/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://blog.shuaizhang.cc/en-us/posts/model-context-protocol-deep-dive/</guid><description>The main content of this article is to deeply understand and compare the evolution and feature sets of the current (February 19, 2026) version of the Model Context Protocol (MCP), as well as the level of support for the standard by MCP server/client frameworks. The primary purpose of this article is to support team decision-making when using MCP, including which feature sets should be adopted, which should be prohibited, and the degree of compatibility with other non-AI-specific communication protocols, such as gRPC. The implementation aspect mainly covers the Python and C# ecosystems.</description></item></channel></rss>