An Open-Source Genesys Cloud Tool Shows AI Admin Access Can Be Safe by Design — But Only the Design You Can Read
Ryan Shatzkamer, Director of Technical Services at outboundIQ, a contact centre technology firm serving 1,000 customers across North America, released genesys-mcp on 24 August 2026. It's a free, MIT-licensed open-source tool that lets Genesys Cloud administrators describe a call flow in plain English to an AI assistant such as Claude, which composes it, draws a diagram inside the chat window, and — only after the administrator approves — publishes it live into Genesys Architect. The tool covers queues, skills, users, wrap-up codes and full call flows, contains no delete functions anywhere in its code, runs inside the administrator's own Cloudflare account so credentials never leave the organisation, and connects to Claude or ChatGPT as a standard OAuth 2.1 connector rather than a custom install.
What does it actually let an admin do?
An admin types a request in plain English, the assistant drafts a Genesys Architect call flow, shows it as a diagram, and waits for explicit sign-off before publishing.
In the demo Shatzkamer published with the release, he asked for a flow that greets callers, offers weekend support on one keypress, and ends the call on another. The assistant referenced the existing queue, drew the full flow, and held it until approved — Shatzkamer says the finished flow was published and validated by Genesys' own platform shortly after. The same tool can also diagram flows an organisation already runs, which is arguably the more useful feature for support teams sitting on undocumented IVR logic they inherited rather than built.
Is the "no delete" promise actually a safety guarantee?
Only partly — it's a constraint this one project chose to build in, not something Genesys enforces, and it hasn't had independent security review.
Permissions are scoped through the organisation's own OAuth client role and enforced by Genesys, which is a reasonable architecture. But the absence of delete tools is a design choice by a single developer, checked by that developer's own claims rather than a third-party audit. That's not a knock on the intent — publishing MIT-licensed code you can read is a genuinely stronger trust position than a vendor telling you to take their word for it. It just means the burden of checking sits with whoever installs it, via the public GitHub repo and issue tracker Shatzkamer says will double as the project's roadmap.
Why should support software buyers outside Genesys shops care?
Because it's an early, concrete example of natural-language admin agents reaching contact-centre configuration, not just chat replies.
This site has already flagged that AI vendor claims are getting harder to tell apart on marketing alone, and that CX vendors are diverging in how seriously they take AI governance. A tool that lets an AI assistant hold administrative access to your call routing — even a carefully fenced one — is exactly the kind of feature buyers should expect their own CCaaS or live-chat vendor to eventually offer, officially or not. The interesting question isn't whether this specific tool is safe; it's whether your vendor's roadmap has an answer for this at all.
What should you ask your own vendor before letting AI touch live configuration?
Ask who approves changes before they go live, whether delete actions are possible, and where credentials and logs are stored.
Specifically: is there a mandatory human approval step, or can the assistant act unattended? Is the audit trail visible to your team or only to the vendor? And critically — has the access-control design been reviewed by anyone other than the person who wrote it? Genesys-mcp answers all three in its documentation; plenty of vendor "AI copilot" features currently don't.
Frequently asked questions
Is genesys-mcp an official Genesys product?
No. It's an independent open-source project built by an outboundIQ employee, not developed or endorsed by Genesys itself.
Does it work with platforms other than Genesys Cloud?
Not this specific tool, but Shatzkamer has previously built a similar natural-language integration for Five9 and a separate IVR visualisation tool.
What does genesys-mcp cost?
Nothing. It's free and MIT licensed, available now on GitHub.
Sources: OutboundIQ's Ryan Shatzkamer Releases Open-Source Tool That Builds Genesys Cloud Call Flows From Plain English, Newsfile Corp, 24 August 2026.