Skip to content

Genesys Cloud MCP connector

The Genesys Cloud connector brings your contact center's virtual agents, alerts and alerting rules to Claude, ChatGPT, Cursor and Microsoft Copilot, with every request running under the signed-in person's own Genesys Cloud access and recorded in an audit log.

  • App credentials
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which Genesys Cloud alerts are still open from last night?

Working in Genesys Cloud with Elaichi

  • Get single Genesys Cloud agentic virtualagent job by ID
  • Get single Genesys Cloud agentic virtualagent version job by ID
  • Get single Genesys Cloud agentic virtualagent version by ID
Ask anything…
Governance / Audit log Last 24 hours
Genesys Cloud Get single Genesys Cloud agentic virtualagent version by ID Emily Carter · Claude · 9:41 AM Done
Genesys Cloud Get single Genesys Cloud agentic virtualagent version job by ID Emily Carter · Claude · 9:41 AM Done
Genesys Cloud Get single Genesys Cloud agentic virtualagent job by ID Emily Carter · Claude · 9:41 AM Done
Genesys Cloud Create a Genesys Cloud agentic virtualagent version job Megan Brooks · ChatGPT · 9:38 AM Done
Genesys Cloud Create a Genesys Cloud agentic virtualagent version Ryan Hayes · Cursor · 9:35 AM Done

How to connect Genesys Cloud to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Genesys Cloud MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Genesys Cloud MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Genesys Cloud MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Genesys Cloud MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Genesys Cloud MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Genesys Cloud to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Genesys Cloud through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Genesys Cloud is logged.

  • Support

    Catch up on overnight alerts

    Ask which Genesys Cloud alerts are still open before the morning huddle, and clear the ones the night shift already handled without opening the console.

  • Contact center operations

    Tune a noisy alerting rule

    Raise the threshold on an alerting rule that fires too often, or remove the rules nobody acts on, by describing the change in plain language.

  • Customer experience

    Draft the next virtual agent version

    Create a new version of a virtual agent, compare it with the version that is live, and update it before it goes in front of customers.

  • IT

    Know what is live before a change

    List every virtual agent in the organization with its current version so a change window starts from a known state.

  • Workforce management

    Clear a batch of alerts at once

    Once the staffing gap behind a run of queue alerts is fixed, update or delete the whole batch in one ask instead of one at a time.

  • Quality

    Check whether a build job finished

    Ask whether a virtual agent version job has completed and what it produced, without waiting for someone to look it up.

Try asking

  • “Which Genesys Cloud alerts are still open from last night?”
  • “List every virtual agent and its current version.”
  • “Raise the threshold on the abandoned calls alerting rule.”

See all 3141 Genesys Cloud tools →

What connecting Genesys Cloud gets you

6 screens from Elaichi, each doing one job for your Genesys Cloud account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which Genesys Cloud alerts are still open from last night?

List every virtual agent and its current version.

Raise the threshold on the abandoned calls alerting rule.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Genesys Cloud alerts in plain language.

Open alerts, virtual agents and alerting rules answered from live Genesys Cloud records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint puts Genesys Cloud in every client.

Claude, ChatGPT and Cursor reach Genesys Cloud through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
Genesys Cloud agentic virtualagent jobs bulk delete Delete Start the deletion of a virtualAgent. (DELETE /api/v2/agentic/virtualagents/{virtualAgentId}/jobs) Requires permission agentic:virtualAgentJob:add. Required: virtual_agent_id.
Get single Genesys Cloud agentic virtualagent job by ID Get Get a virtualAgent job. (GET /api/v2/agentic/virtualagents/{virtualAgentId}/jobs/{jobId}) Requires permission agentic:virtualAgentJob:view. The id is the jobId. Required: id, virtual_agent_id.
Create a Genesys Cloud agentic virtualagent version job Create Start the publishing of a virtual agent version. (POST /api/v2/agentic/virtualagents/{virtualAgentId}/versions/{versionId}/jobs) Requires permission agentic:virtualAgentVersionJob:add. Required: virtual_agent_id, version_id, virtualAgentVersion.
Get single Genesys Cloud agentic virtualagent version job by ID Get Get the status of the publishing job for this virtual agent version. (GET /api/v2/agentic/virtualagents/{virtualAgentId}/versions/{versionId}/jobs/{jobId}) Requires permission agentic:virtualAgentVersionJob:view. The id is the jobId. Required: id, virtual_agent_id, version_id.
Create a Genesys Cloud agentic virtualagent version Create Create a virtual agent version. When validateOnly is true, the request is validated without creating a version. (POST /api/v2/agentic/virtualagents/{virtualAgentId}/versions) Requires permission agentic:virtualAgentVersion:add. Required: virtual_agent_id, definition.

Tool catalog

3141 Genesys Cloud tools, no code required.

Virtual agents, alerts, alerting rules and jobs, cataloged by resource and method.

ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Genesys Cloud · open alerts and queues

Genesys Cloud starter 18 Mar 4, 2026

Contact center operations toolbox

Genesys Cloud · alerting rules and thresholds

— 9 Mar 2, 2026

Customer experience toolbox

Genesys Cloud · virtual agents and versions

— 24 Feb 27, 2026

IT toolbox

Genesys Cloud · org inventory and change windows

Genesys Cloud starter 6 Feb 19, 2026

Workforce management toolbox

Genesys Cloud · staffing alerts in bulk

— 31 Jan 30, 2026

Quality toolbox

Genesys Cloud · virtual agent jobs and releases

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Genesys Cloud toolbox.

Support works with alerts, CX works with virtual agents, each toolbox scoped to one team.

ElaichiConnections
Connection Scope Status Access
GE

Genesys Cloud (Support)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GE

Genesys Cloud (Contact center ops)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GE

Genesys Cloud (CX EMEA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GE

Genesys Cloud (IT)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GE

Genesys Cloud (Workforce)

Connected by Ryan Hayes

Personal • Active Not shared
GE

Genesys Cloud (Quality)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Genesys Cloud without seeing credentials.

One person connects Genesys Cloud, shares it with teams, and nobody else handles a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Genesys Cloud Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Genesys Cloud Virtual agents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Genesys Cloud Virtual agents List Toolbox

Audit log

Every Genesys Cloud call names who did it.

When, who, what happened, type and resource, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Genesys Cloud digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch virtual agents

    Genesys Cloud

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Genesys Cloud

    Queued

Workflows

A schedule drafts the Genesys Cloud alert digest.

Alerts are fetched, grouped, drafted into a digest, approved by a person, then posted back.

Genesys Cloud health

Refreshed 4 minutes ago · every 15 minutes · from the virtual agents collection

Live

Virtual agents

1,284 ↓ 12%

Alerts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Virtual agents created

Last 14 days

By team

Share of activity

Support 34%

Contact center ops 27%

CX EMEA 21%

IT 18%

Collections and dashboards

Genesys Cloud health, computed without a model.

Four metrics, fourteen days of alerts created, and a breakdown by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Genesys Cloud

All three can connect Genesys Cloud to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Genesys Cloud, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Genesys Cloud tools Allow or restrict single Genesys Cloud tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Genesys Cloud call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Genesys Cloud tools for your AI agents

3141 tools are ready to call through Elaichi's MCP endpoint the moment you connect Genesys Cloud, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 238 of 3141 Genesys Cloud tools here. Connect Genesys Cloud and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

How do I connect Genesys Cloud to Claude?

Connect Genesys Cloud in Elaichi first, where you sign in with your Genesys Cloud app credentials, with no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself when Claude asks, and Genesys Cloud is ready to use.

Does Genesys Cloud work with ChatGPT and Cursor as well as Claude?

Yes. Once Genesys Cloud is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Genesys Cloud once and every client picks it up.

What can an AI agent actually do with my Genesys Cloud data?

With Genesys Cloud connected, an agent can list open alerts, update or clear them in bulk, create and adjust alerting rules, and create, review and update virtual agents and their versions. It can also check on virtual agent jobs and report what they produced. Short concrete asks, like "show me open alerts for the billing queue", work better than long paragraphs.

Does connecting Genesys Cloud give the AI access to my whole org?

No. Every request to Genesys Cloud runs as the person who signed in, so the agent sees exactly the queues, alerts and virtual agents that person's Genesys Cloud role already allows, and nothing more. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Genesys Cloud grants.

Can my team share one Genesys Cloud connection?

Yes. One person connects Genesys Cloud in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Genesys Cloud action.

Can I stop an agent from deleting or changing things in Genesys Cloud?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting alerting rules or updating virtual agents for a role or for one person while leaving read actions open. A restricted Genesys Cloud action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to a Genesys Cloud connection when someone leaves?

Offboarding someone in Elaichi ends their Genesys Cloud access at once, in every client they used. If they had shared a Genesys Cloud connection with a team, it keeps working for everyone else. Disconnecting Genesys Cloud once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Does the Genesys Cloud MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Genesys Cloud is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Genesys Cloud?

Yes. Both let Claude, ChatGPT or Cursor use Genesys Cloud. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Genesys Cloud call.

How is Elaichi different from Composio for Genesys Cloud?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Genesys Cloud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Genesys Cloud in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot