frafat
02/10/2026, 10:07 PM"Not connected" — no matter the tool, no matter the parameters.
My setup:
Single-prompt agent (restaurant booking assistant) with a custom MCP server (~10 tools: searchReservationsByPhone, getDaySlots, createReservation, updateReservation, cancelReservation, getWeeklyAvailability, getMenuOverview, getCompanyInfo, etc.)
What works:
✅ Production calls — all MCP tools execute correctly
✅ UI Chat Test — MCP handshake + tool execution works
✅ Voice Test — no issues
✅ Dynamic variables resolve correctly everywhere
What's broken:
❌ LLM Simulation Testing — every MCP tool returns "Not connected"
❌ Batch Simulation Testing — same across all test cases
This is not an MCP server issue. The server is reachable, stable, and works in every other context. The simulation runner simply cannot execute MCP tool calls.
I built 10 test cases covering reservation flows, modifications, cancellations, menu queries, and edge cases — all fail because every tool returns "Not connected". This makes simulation and batch testing completely unusable for anyone using MCP.
Can the team please confirm if this is a known limitation or a bug? Is a fix on the roadmap? This is a serious blocker for building production-grade agents with MCP.
Thanks 🙏
https://cdn.discordapp.com/attachments/1470904019168792637/1470904020507033692/WhatsApp_Image_2026-02-10_at_23.07.06.jpeg?ex=698cfd9e&is=698bac1e&hm=e11dc85a115edb1f9d3158605fc802723b06feebe80c2d068625f3ec9fd0e4e1&Shehroze -Support @Retell
02/11/2026, 1:33 PMShehroze -Support @Retell
02/11/2026, 1:34 PMShehroze -Support @Retell
02/11/2026, 7:31 PMfrafat
02/12/2026, 12:50 AMShehroze -Support @Retell
02/25/2026, 9:29 PM