From 8d3189f8aaad877589634e7769d438a86f7b5984 Mon Sep 17 00:00:00 2001 From: Y M <90426808+yuka-with-data@users.noreply.github.com> Date: Thu, 16 Apr 2026 12:40:44 -0700 Subject: [PATCH 1/3] Doc: Clarify MCP client-server model in What is MCP? section --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 487d48bee..7ee2a4a51 100644 --- a/README.md +++ b/README.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) From bc28212a553e8293be414e566bae4abcbedc63de Mon Sep 17 00:00:00 2001 From: Y M <90426808+yuka-with-data@users.noreply.github.com> Date: Wed, 22 Apr 2026 13:15:30 -0700 Subject: [PATCH 2/3] Restore README.md to upstream version -v1 is frozen --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 7ee2a4a51..487d48bee 100644 --- a/README.md +++ b/README.md @@ -207,11 +207,7 @@ 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 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: +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: - 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) From 1e1661f095c9d2c1acc2dfaf1a4830e379ad489f Mon Sep 17 00:00:00 2001 From: Y M <90426808+yuka-with-data@users.noreply.github.com> Date: Wed, 22 Apr 2026 14:04:14 -0700 Subject: [PATCH 3/3] Update README v2 -v1 frozen --- README.v2.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.v2.md b/README.v2.md index d0851c04e..763cccbb3 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)