Super admin losing team call access in the RingEX Phone MCP after the Nov 17 legacy removal: is there an admin path?
Hi
I own a small insurance agency and I'm the Super Admin on our RingCentral account. We use the RingEX Phone MCP with Claude every business day to build call recaps for each producer and a shared call summary for management.
Today this works because the legacy tools (list_user_call_log, read_call_ai_notes, search_directory_entries) accept an extensionId / ownerExtensionId, and my Super Admin role lets me read the call log and AI notes for any extension on the account.
Those tools are marked for removal on November 17. The replacements (get_my_call_activity, get_my_call_insight, search_my_call_insights) only return the signed-in user's calls. The get_my_phone description says "an administrator token cannot select another user." I tested get_my_call_activity with my Super Admin login, and it returned only my own extension's calls.
We do have ACE, but I'd much rather keep this on the Claude connector. In Claude it works alongside our other connectors (email, calendar, our agency management system, shared docs), so one workflow can read a call, draft the follow-up, update the client record and build the recap. Routing everything through ACE separately breaks that.
My questions:
1. Can you confirm that after November 17 there's no way for a Super Admin to read other extensions' call logs and AI notes through the RingEX Phone MCP?
2. Is an admin-scoped option planned, either an extension selector on the new tools for users with the right role or an admin AI notes tool on the RingEX Admin server? If so, is there a timeline?
3. Can the November 17 removal be extended for accounts that depend on it until an admin option exists?
4. Is there an official ACE MCP server, or a supported way to use ACE data inside Claude next to the other RingCentral MCP servers? I saw a "ringcentral-conversation-intelligence" plugin on GitHub and wasn't sure whether it's official.
5. Does read_company_call_log on the RingEX Admin server need the ReadCompanyCallLog role permission, same as the REST endpoint?
Part of why I'm asking: I own the account, pay for the subscription and hold Super Admin, so I'd expect my AI tools to see what my role already allows. Any guidance on the right path before the 17th would really help.
Thanks!