xenial-black•3mo ago
I am encountering an error with the GHL integration.
{
"name": "get_free_slots",
"role": "tool_call_result",
"time": 1750231992953,
"result": "{"error": "Failed to connect to MCP server"}",
"toolCallId": "call_rbpCatHIzkPKdwOD7fQP8euw",
"secondsFromStart": 42.128
}
I am getting this error while using the AI voice agent for outbound calls. I had completed the GHL integrations in the VAPI voice agents, and it was working fine until yesterday. Now, I am encountering this error.
7 Replies
Thank you for sharing the error details. The message "Failed to connect to MCP server" suggests a connectivity or authentication issue between your Vapi agent and the MCP server, which is required for GHL tool calls.
To help diagnose further, have you recently changed your MCP server URL, API key, or network settings? If not, are you able to access the MCP server endpoint (e.g.,
https://mcp.vapi.ai/mcp) from your environment?
If everything appears unchanged, you may also want to check the Vapi status page or reach out to Vapi support or their Discord community for real-time assistance.
Sources:
- Vapi MCP Server Documentation
- Vapi GoHighLevel Integration Guide
- Vapi Support⤵️ Mention @Vapi Support Bot for follow-ups 🐥
xenial-blackOP•3mo ago
Thanks for the response. I haven’t configured any custom MCP setup on my end. I’m just using the predefined tools available in the Vapi dashboard and only passing parameters like the contact ID, etc.
Everything was working fine for the past three days without any issues. I haven’t made any changes to my configuration, so I’m not sure why this error is suddenly appearing today.
Would appreciate your help in resolving this.
fair-rose•3mo ago
looking into it
vicious-gold•3mo ago
thanks king- @bhargav let me know once there’s a solution!
curly-silver•3mo ago
Hey there, could you please share your call ID so I can investigate the potential issues you're experiencing?
xenial-blackOP•3mo ago
@Shubham Bajaj Hey, my call id is 8929c903-e043-49ad-996e-bb3282e3f22f
Hey Bhargav, could you please try again and let me know how it goes for you? The issue was on our side, and it has been fixed by the team.