From a9381263275a86257002c1e34101c1dce70cbc05 Mon Sep 17 00:00:00 2001
From: yukawithdata <90426808+yuka-with-data@users.noreply.github.com>
Date: Tue, 2 Jun 2026 09:32:53 -0700
Subject: [PATCH] Doc: Clarify MCP Client-Server model in What is MCP section
 (#2459)

---
 README.v2.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.v2.md b/README.v2.md
index a888f21b..bae230c3 100644
--- a/README.v2.md
+++ b/README.v2.md
@@ -207,7 +207,11 @@ In the inspector UI, connect to `http://localhost:8000/mcp`.
 
 ## What is MCP?
 
-The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) lets you build servers that expose data and functionality to LLM applications in a secure, standardized way. Think of it like a web API, but specifically designed for LLM interactions. MCP servers can:
+The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) lets you build servers that expose data and functionality to LLM applications in a secure, standardized way. Think of it like a web API, but specifically designed for LLM interactions.
+
+MCP follows a **client-server model**, where LLM applications act as clients and connect to MCP servers to access capabilities such as data retrieval and tool execution in a consistent format.
+
+MCP servers can:
 
 - Expose data through **Resources** (think of these sort of like GET endpoints; they are used to load information into the LLM's context)
 - Provide functionality through **Tools** (sort of like POST endpoints; they are used to execute code or otherwise produce a side effect)