Connecting MCP Server to Dust: Troubleshooting Connection Errors | Dust Community

Connecting MCP Server to Dust: Troubleshooting Connection Errors

Hey guys, I’m currently trying to connect our MCP server to Dust. But when adding it fails saying there is an error. When looking at the inspector, I can see the error is : Error fetching remote server metadata, URL may be invalid. Our MCP url is something like this : xxxx.com/mcp?apiKey=abc It’s working well on cursor. Thanks in advance 🙏

15 comments

Remi
·
·
Thanks for the question Guillaume Lacoste! Looping in our MCP expert Sébastien Flory 👀
🙌1
Sébastien Flory
·
·
Hello
Sébastien Flory
·
·
How does it far with the MCP inspector ?
Sébastien Flory
·
·
https://modelcontextprotocol.io/docs/tools/inspector
Guillaume Lacoste
·
·
hey, it’s working well.
Sébastien Flory
·
·
can you send me the full URL privately so I can test? (maybe we don't like "?...")
David Ebbo
·
·
FWIW, I have an Azure Function MCP server that takes a key using ?code=xyz and that works fine, so the query string doesn't appear to be a problem.
David Ebbo
·
·
Guillaume Lacoste I think the problem is that your /mcp endpoint expects streamable http, while Dust only supports SSE. Try changing the URL to https://mcp.wisekudu.com/sse.
Guillaume Lacoste
·
·
Are you sure ? The placeholder show as example the /mcp way (streamable http)
David Ebbo
·
·
I just tried it and it worked. Give it a try.
Guillaume Lacoste
·
·
Yes just tried it also, and it’s working well.
👍1
Sébastien Flory
·
·
So to sum up you were using streamable http vs sse ?
Sébastien Flory
·
·
We'll add support for streamable HTTP asap.
Guillaume Lacoste
·
·
Yes, actually mcp deprecated sse over streamable http: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http But as it’s super recent, lot of client doesn’t support yet streamable http. So I added backwards compatibility for sse, and just swap the url to sse. Thanks for the help 🙏
Sébastien Flory
·
·
We'll support streamable http & auth asap.
🙌1
👍1