<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mcp on Ou David | Systems Engineer</title><link>https://preview.vvivid.dev/tags/mcp/</link><description>Recent content in Mcp on Ou David | Systems Engineer</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 24 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://preview.vvivid.dev/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding JSON-RPC: The Protocol Behind MCP</title><link>https://preview.vvivid.dev/posts/json_rpc_the_protocol_behind_mcp/</link><pubDate>Sun, 24 Aug 2025 00:00:00 +0000</pubDate><guid>https://preview.vvivid.dev/posts/json_rpc_the_protocol_behind_mcp/</guid><description>&lt;p&gt;I&amp;rsquo;ve been diving into the &lt;a href="https://modelcontextprotocol.io/"&gt;Model Context Protocol (MCP)&lt;/a&gt; lately. Honestly, it&amp;rsquo;s the most exciting thing happening in AI infrastructure right now. But here&amp;rsquo;s the thing: to really understand MCP, you need to understand &lt;a href="https://www.jsonrpc.org/specification"&gt;JSON-RPC&lt;/a&gt; first. That&amp;rsquo;s what MCP is built on.&lt;/p&gt;
&lt;p&gt;So let me break down JSON-RPC for you. Once you get this, MCP will make way more sense.&lt;/p&gt;
&lt;p&gt;First, let&amp;rsquo;s talk about how JSON-RPC is different from the REST APIs we&amp;rsquo;re all used to. REST is stateless and unidirectional where each request is independent. Check this out:&lt;/p&gt;</description></item></channel></rss>