From 99f588cb75b405808b1de71a824a530b79a14fd3 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com> Date: Wed, 2 Jul 2025 12:54:01 +0000 Subject: [PATCH 1/2] 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 --- docs/core_concepts/51_mcp/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core_concepts/51_mcp/index.mdx b/docs/core_concepts/51_mcp/index.mdx index 76c42d6a..fa453a22 100644 --- a/docs/core_concepts/51_mcp/index.mdx +++ b/docs/core_concepts/51_mcp/index.mdx @@ -35,7 +35,7 @@ https://app.windmill.dev/api/w//mcp/sse?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: From 92dd9363318a29a716a6d5ae2efb5fe01fe5eea9 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com> Date: Wed, 2 Jul 2025 13:49:45 +0000 Subject: [PATCH 2/2] 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 --- docs/core_concepts/51_mcp/index.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/core_concepts/51_mcp/index.mdx b/docs/core_concepts/51_mcp/index.mdx index fa453a22..b1cb0cb8 100644 --- a/docs/core_concepts/51_mcp/index.mdx +++ b/docs/core_concepts/51_mcp/index.mdx @@ -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. ---