Hi ! We are actually using HTTP

Hi ! We are actually using HTTP streamable 😅 Do you have issues connecting with some clients ?

11 Replies

hello, thanks for looking into this. We are attempting to integrate MCP with Dify. However, Dify only supports HTTP streamable MCP servers, and the MCP URL generated by Windmill (with the /sse endpoint) fails to configure

VirendraPawar•2d ago

I have also tried using the same MCP URL with /mcp trialing endpoint, but still it does not work. Thanks once again @Farhad

VirendraPawar•2d ago

Also, at times it returns with this error too.

centdix974OP•2d ago

The only url we have is the /sse endpoint, we kept the /sse trailing for backward compatibility but we are using http streamable That is weird, so it refuses to connect every time or sometimes it works then throws an error ?

VirendraPawar•2d ago

it is not working at all. This is how I am configuring it.

centdix974OP•2d ago

I'll take a look into this I'll let you know

VirendraPawar•2d ago

Thank you 😄

VirendraPawar•2d ago

I also tried to use this with MCP aggregators, but Windmill's MCP is not configurable with tools I have tried so far except Cursor IDE https://github.com/adamwattis/mcp-proxy-server

> mcp-proxy-server@0.1.0 dev:sse
> nodemon --watch 'src/**' --ext 'ts,json' --ignore 'src/**/*.spec.ts' --exec 'tsx src/sse.ts'

[nodemon] 3.1.9
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src/**
[nodemon] watching extensions: ts,json
[nodemon] starting `tsx src/sse.ts`
Connecting to server: windmill
Failed to connect to windmill: Error: SSE error: {"code":401,"message":"Non-200 status code (401)"}
    at EventSource._eventSource.onerror (/tmp/mcp-proxy-server/node_modules/@modelcontextprotocol/sdk/src/client/sse.ts:36:23)
    at EventSource.failConnection_fn (/tmp/mcp-proxy-server/node_modules/eventsource/src/EventSource.ts:534:21)
    at <anonymous> (/tmp/mcp-proxy-server/node_modules/eventsource/src/EventSource.ts:371:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

> mcp-proxy-server@0.1.0 dev:sse
> nodemon --watch 'src/**' --ext 'ts,json' --ignore 'src/**/*.spec.ts' --exec 'tsx src/sse.ts'

[nodemon] 3.1.9
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src/**
[nodemon] watching extensions: ts,json
[nodemon] starting `tsx src/sse.ts`
Connecting to server: windmill
Failed to connect to windmill: Error: SSE error: {"code":401,"message":"Non-200 status code (401)"}
    at EventSource._eventSource.onerror (/tmp/mcp-proxy-server/node_modules/@modelcontextprotocol/sdk/src/client/sse.ts:36:23)
    at EventSource.failConnection_fn (/tmp/mcp-proxy-server/node_modules/eventsource/src/EventSource.ts:534:21)
    at <anonymous> (/tmp/mcp-proxy-server/node_modules/eventsource/src/EventSource.ts:371:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

GitHub

GitHub - adamwattis/mcp-proxy-server: An MCP proxy server that aggr...

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface - adamwattis/mcp-proxy-server

centdix974OP•2d ago

I looked into Dify a little bit and it's seems the issue is on their hand as their requests are not following the standards on http streamable communication but I'll let you know if I find something for this it seems they do not handle http streamable servers, only sse

centdix974OP•2d ago

I did not test this myself but this one for example seems to handle it correctly https://github.com/TBXark/mcp-proxy

GitHub

GitHub - TBXark/mcp-proxy: An MCP proxy server that aggregates and ...

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single HTTP server. - TBXark/mcp-proxy

VirendraPawar•22h ago

Hi @Farhad, thanks for investigation and investing your time into this. I can't thank you enough for this. Lately, I also found a possible way: using 1mcp/agent for aggregation which acts as a bridge between Windmill and Dify. I consider the issue to be resolved for now. Thanks once again for your time.

Hi ! We are actually using HTTP

Did you find this page helpful?