<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>MCP on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/mcp/</link><description>Recent content in MCP on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 16 Apr 2026 19:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>A Markdown's Three Lives: From Static Rules to Git-Backed MCP Server</title><link>https://blog.chuanxilu.net/en/posts/2026/04/from-markdown-to-mcp-server-gear-protocol/</link><pubDate>Thu, 16 Apr 2026 19:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/04/from-markdown-to-mcp-server-gear-protocol/</guid><description>Aristotle&amp;#39;s reflection rules started as a flat Markdown file — append-only, forgotten, no rollback. When dozens of rules accumulated, I realized the file wasn&amp;#39;t enough. This started a design iteration path from append-only to Git-backed MCP Server. That path led to something called GEAR.</description></item></channel></rss>