MCPs refuses to connect
this is making me go crazy, the server is clearly connecting on the backend yet this somehow fails, and no detailed error? what does not connected mean ðŸ˜
i even have eventsouce, eventsource extended installed
also tried streamable http
i also have "use node" on the top n everything, please liberate me. I couldn't sleep the entire night.
mcp ts docs:
https://github.com/modelcontextprotocol/typescript-sdk#writing-mcp-clients
GitHub
GitHub - modelcontextprotocol/typescript-sdk: The official Typescri...
The official Typescript SDK for Model Context Protocol servers and clients - modelcontextprotocol/typescript-sdk

5 Replies
plus the debugging process was horrible as well the console kept on showing dangling promises, and i never leave my promises dangling, am a man of my wrds
this thing took 10 yrs off my life n still no solution

console logs
the backend just crashes after 1 dangling promise error
itz easier to show the issue on call
ok it seems its not an mcp issue
but the database mutation having the issue

update: after setting the rust log level to debug in backend, the issue seems to be cuz of size limits
+ add better error reporting
ugh ig ill have to breakdown the chunks