Hi,that usually happens with new GHL accounts MCP connections often break due to API key scopes, sub-account context, or OAuth permissions not being re-initialized. If it worked before, the setup logic is fine; it’s almost always an auth or account level mismatch. I’ve helped debug this exact VAPI ↔ GHL issue a few times. If you want, tell me whether you’re connecting at agency or sub-account level and what error MCP throws I can point you to the fix pretty fast.