docs: add precision about HTTP streamable transport layer to MCP docs (#1034)

* docs: add precision about HTTP streamable transport layer to MCP docs

Add clarification that the Windmill MCP server uses HTTP streamable as the transport layer and MCP clients should be configured to use that protocol.

Fixes #1033

Co-authored-by: Ruben Fiszel <[email protected]>

* docs: add HTTP streamable troubleshooting to MCP docs

Add troubleshooting information about ensuring MCP clients use HTTP streamable transport protocol when experiencing connection issues.

Co-authored-by: centdix <[email protected]>

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: Ruben Fiszel <[email protected]>
Co-authored-by: centdix <[email protected]>
Co-authored-by: Henri Courdent <[email protected]>

Author: 4 people

docs/core_concepts/51_mcp/index.mdx

@@ -35,7 +35,7 @@ https://app.windmill.dev/api/w/<your-workspace-id>/mcp/sse?token=<your-token>
 
 ### Connect your LLM to Windmill
 
-Most modern LLM agents and interfaces now support MCP as a plug-and-play integration. Here are some examples configurations, for Claude Desktop and Cursor.
+Most modern LLM agents and interfaces now support MCP as a plug-and-play integration. The Windmill MCP server uses **HTTP streamable** as the transport layer, and MCP clients should be configured to use that protocol. Here are some examples configurations, for Claude Desktop and Cursor.
 
 To connect with Cursor:
 
@@ -97,6 +97,9 @@ Claude will:
 - **My LLM does not find the correct script/flow to run**
   - Ensure the script or flow is deployed and visible in your workspace.
   - Choose good titles and descriptions to help the LLM find the correct script/flow.
+- **Client has issues connecting to the MCP server**
+  - Make sure your MCP client is configured to use **HTTP streamable** as the transport protocol.
+  - Verify that your MCP URL is correct and the token is valid.
 
 ---