From b65286c80e989b5f47a22b300f1eb37412c8c2fb Mon Sep 17 00:00:00 2001
From: Ramitha Iddamalgoda <141983882+Rami2212@users.noreply.github.com>
Date: Tue, 21 Apr 2026 20:11:05 +0530
Subject: [PATCH 1/2] Update MCP documentation on transport mechanisms

Clarify MCP transport support: restrict API Platform to HTTP/SSE and document stdio as local only.
---
 en/docs/mcp-servers/get-started-with-mcp.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/en/docs/mcp-servers/get-started-with-mcp.md b/en/docs/mcp-servers/get-started-with-mcp.md
index 34a73369b..d39b85969 100644
--- a/en/docs/mcp-servers/get-started-with-mcp.md
+++ b/en/docs/mcp-servers/get-started-with-mcp.md
@@ -6,10 +6,22 @@ MCP is a JSON-RPC–based protocol designed to standardize how applications inte
 
 MCP follows a host–client–server architecture and supports two primary transport mechanisms: stdio and streamable HTTP. While stdio is commonly used for local communication between clients and servers on the same machine, streamable HTTP is increasingly preferred for remote connections, especially as MCP adoption grows across networked environments. 
 
+> **Note:**  
+> The Model Context Protocol defines both `stdio` and streamable HTTP transports.  
+> - `stdio` is designed for **local, process-level communication** (for example, between a CLI/IDE and a locally running MCP server).  
+> - Streamable HTTP (SSE) is designed for **remote, network-based communication**.  
+>  
+> **MCP servers deployed on the WSO2 API Platform are hosted and accessed over the network. Therefore, only streamable HTTP (SSE) transport is supported.**  
+> MCP clients connecting to API Platform must be configured to use HTTP/SSE, not `stdio`.
+
 For more information, refer to the official [specification](https://modelcontextprotocol.io/introduction).
 
 ## Remote MCP Servers with API Platform
 
+> **Transport Requirement:**  
+> Since API Platform exposes MCP servers as **remote, network-accessible endpoints**, it **does not support `stdio` transport**.  
+> All MCP interactions with API Platform must use **streamable HTTP (SSE)**.
+
 API Platform now includes support for MCP servers. It provides a complete solution for transforming existing APIs into intelligent, AI-ready tools. With a centralized control plane, API Platform simplifies the entire lifecycle of MCP server management—from creation to discovery—delivering a seamless experience for both API developers and AI agent builders. Additionally, API Platform allows you to customize the developer portal to deliver a tailored, MCP-only experience for your consumers.
 
 ![MCP Inspector](../assets/img/introduction/mcp/mcp-architecture.png)

From 3b198cefec2b041498b8207302be00fa9909df23 Mon Sep 17 00:00:00 2001
From: Ramitha Iddamalgoda <141983882+Rami2212@users.noreply.github.com>
Date: Wed, 22 Apr 2026 13:04:55 +0530
Subject: [PATCH 2/2] Update en/docs/mcp-servers/get-started-with-mcp.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 en/docs/mcp-servers/get-started-with-mcp.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en/docs/mcp-servers/get-started-with-mcp.md b/en/docs/mcp-servers/get-started-with-mcp.md
index d39b85969..f82cc5f8f 100644
--- a/en/docs/mcp-servers/get-started-with-mcp.md
+++ b/en/docs/mcp-servers/get-started-with-mcp.md
@@ -12,7 +12,7 @@ MCP follows a host–client–server architecture and supports two primary trans
 > - Streamable HTTP (SSE) is designed for **remote, network-based communication**.  
 >  
 > **MCP servers deployed on the WSO2 API Platform are hosted and accessed over the network. Therefore, only streamable HTTP (SSE) transport is supported.**  
-> MCP clients connecting to API Platform must be configured to use HTTP/SSE, not `stdio`.
+> MCP clients connecting to API Platform must be configured to use streamable HTTP (SSE), not `stdio`.
 
 For more information, refer to the official [specification](https://modelcontextprotocol.io/introduction).