Since Streaming HTTP is not yet supported, I am trying to connect using SSE. This reports error connecting with HTTP Stauts 500.

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

i am tring to connect the mcp tool with vapi ai from n8n and today it is occurring problems http req 500 error 1. Tool id: cc4f16bb-f2af-434f-83e8-33316bc6bb67 2. Mcp url link: https://waitsmart.app.n8n.cloud/mcp/6114acac-a3aa-4404-8d1b-6640256c78f4/sse 3. Response Body error: { "error": "Failed to connect to MCP server: SSE error: Failed to fetch" } 4. Request failed with status: 500 https://cdn.discordapp.com/attachments/1395709771809685504/1396218525575807046/image.png?ex=687d4954&is=687bf7d4&hm=14c9a4d7bfe740b0365857c90f08888810152461a1d355f2410d99aadc63214b& https://cdn.discordapp.com/attachments/1395709771809685504/1396218526322266122/image.png?ex=687d4955&is=687bf7d5&hm=dfa828d5b667b0a6f9f3b330573ee6febd7f0cc2300f44383f7289e36114610e&

Hi galoremate, It seems you're encountering an HTTP 500 error while trying to connect your MCP tool with the SSE protocol. Here are a few steps to help troubleshoot the issue: 1. **Verify MCP Server Configuration**: Ensure your MCP server is configured correctly to support SSE, as the connection errors can often be due to server-side misconfiguration. 2. **Response Format**: Check that the server response is in the correct JSON format and adheres to expected structures, as deviations can lead to connection issues. 3. **Authorization Headers**: Ensure that your request to the MCP server includes the necessary authorization headers, such as the

Authorization: Bearer YOUR_API_KEY

. Double-check that your server handles authorization properly. 4. **Server Logs**: Review your MCP server logs for any errors that might help identify specific issues causing the failure. Logs can reveal issues like malformed requests or unexpected server errors. 5. **Manual Testing**: Use tools like

curl

to manually test the server endpoint to verify it returns the expected JSON and HTTP status. Compare this to the responses expected by Vapi. If these steps do not resolve the issue, consider logging requests on both client and server sides for deeper insights into request handling and responses. If possible, switching to a supported protocol such as Streamable HTTP may be worthwhile, given that SSE is deprecated. For additional information, you may visit the [Vapi MCP Server documentation](https://docs.vapi.ai/sdk/mcp-server).

I'm getting the same thing. I can reach the MCP server endpoint from my desktop and other hosts and get HTTP 200. When I try to test from VAPI I am also getting HTTP 500. I tried putting in a dummy webhook.site URL into the MCP config in VAPI to look at the raw request, but that also errored with HTTP 500 and webhook.site never recieved the request. Something appears to be getting blocked on the VAPI side - requests are not getting out of the MCP tool node

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team

@Shubham Bajaj can you please help with this HTTP 500 error? I am seeing the exact same behavior, and it looks like a couple of others are as well. The test ping doesn't seem to get out to the internet regardless where the endpoint is

If you would like, I could personally test it from my side with a payload request of your choice. I would be testing it outside of VAPI with POSTMAN most likely as long as I have the auth credentials and your consent.

My MCP server endpoint (hosted in n8n cloud) works fine outside of VAPI. For some reason requests from VAPI do not seem to be getting through. In fact, VAPI MCP config can't seem to access any internet endpoint!

If you are using the test function for the tool in Vapi, it sometimes does not reflect real results. Instead, use a call as a test and review the logs for debugging. If you are not receiving any MCP logs on your server from an actual call with the assistant and toolCall, then there is an issue with one of the sides (and possibly even the tool in VAPI)