MCP server not reachable
Hello we are having an issue with the tools from MCP server since this morning. this is breaking our prod. please help !
VBased on the information I found, here's a first troubleshooting step for your MCP server connectivity issue:
Check your network configuration and firewall settings:
Sources:
Check your network configuration and firewall settings:
- Ensure your firewall allows traffic on necessary ports
- Whitelist
vapi.aiand*.vapi.aidomains - Verify the server URL in your Vapi Dashboard is correct and accessible from outside your network
Sources:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
VBased on the information I found, here's a first troubleshooting step for your MCP server connectivity issue:
Check your network configuration and firewall settings:
Sources:
Check your network configuration and firewall settings:
- Ensure your firewall allows traffic on necessary ports
- Whitelist
vapi.aiand*.vapi.aidomains - Verify the server URL in your Vapi Dashboard is correct and accessible from outside your network
Sources:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
KHey, really sorry for your experience and for your customers' bad experience as well. If possible, could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you.
Also, I'll request you to share your call ID.
Also, I'll request you to share your call ID.
SThe problem i think is that the tool names from the MCP server are being renamed now to server_tool_name when passed to the model, the model then uses the modified name to call the tool except that it's passes as it is (server_tool_name) to the MCP server which responds with a Unknown tool response.
I've seen that the tools naming has been changed recently I think this is what introduced this bug. it was working fine untill yesterday.
I've seen that the tools naming has been changed recently I think this is what introduced this bug. it was working fine untill yesterday.
SThis is the call Id: 2683882d-c4f6-4b27-817a-efc26dcf2f6e
This is the tool Id: 2de1a974-9c29-44fe-a053-84e399a9aaa4
This is the tool Id: 2de1a974-9c29-44fe-a053-84e399a9aaa4
S@Vapi Team Guys anything on this we are blocked by this
KWe will investigate this issue and get back to you shortly.
