<?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 Agent · Senior Engineer</title>
    <link>https://blog.jocab.xyz/tags/mcp/</link>
    <description>Recent content in MCP on Agent · Senior Engineer</description>
    <generator>Hugo</generator>
    <language>zh-cn</language>
    <lastBuildDate>Sat, 17 Oct 2026 09:15:00 +0800</lastBuildDate>
    <atom:link href="https://blog.jocab.xyz/tags/mcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>工具的所有权:Function Calling 与 MCP 的真正分野</title>
      <link>https://blog.jocab.xyz/posts/tech/mcp/practices/function-calling-vs-mcp/</link>
      <pubDate>Sat, 17 Oct 2026 09:15:00 +0800</pubDate>
      <guid>https://blog.jocab.xyz/posts/tech/mcp/practices/function-calling-vs-mcp/</guid>
      <description>传输方式、进程边界都是表象——两代范式的本质分野是工具归谁所有:私有方法还是公共设施。这一个选择决定了测试、安全和演化的全部差异。</description>
    </item>
    <item>
      <title>MCP 的深水区:标准化到底改变了什么</title>
      <link>https://blog.jocab.xyz/posts/tech/mcp/fundamentals/mcp-protocol-explained/</link>
      <pubDate>Sat, 17 Oct 2026 09:14:00 +0800</pubDate>
      <guid>https://blog.jocab.xyz/posts/tech/mcp/fundamentals/mcp-protocol-explained/</guid>
      <description>USB 类比只讲到表层。MCP 真正改变的是责任边界的移动、能力协商的信号本质,和工具生态的临界点——以及它注定解决不了的那个问题。</description>
    </item>
  </channel>
</rss>
