# 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.

Source: https://elaichi.ai/connectors/genesyscloud/

## Facts

| | |
| --- | --- |
| Application | Genesys Cloud |
| Category | Voice |
| AI tools | 3141 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Genesys Cloud is connected

- 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.

## Connect Genesys Cloud in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Genesys Cloud.
2. Optionally set Share with, then press Connect.
3. Paste your Genesys Cloud app credentials. Genesys Cloud authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Genesys Cloud tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Genesys Cloud MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Genesys Cloud MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Genesys Cloud tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Genesys Cloud through Elaichi

### Catch up on overnight alerts

Support. 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.

### Tune a noisy alerting rule

Contact center operations. 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.

### Draft the next virtual agent version

Customer experience. 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.

### Know what is live before a change

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

### Clear a batch of alerts at once

Workforce management. 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.

### Check whether a build job finished

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

## 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.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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.

## All 3141 Genesys Cloud tools

Every tool below is callable through https://api.elaichi.ai/mcp once Genesys Cloud is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **Get single Genesys Cloud agentic virtualagent version by ID** (Get). Get a virtual agent version. (GET /api/v2/agentic/virtualagents/{virtualAgentId}/versions/{versionId}) Requires permission agentic:virtualAgentVersion:view. The id is the versionId. Required: id, virtual_agent_id.
- **Update a Genesys Cloud agentic virtualagent version by ID** (Update). Update a virtual agent version. When validateOnly is true, the update is validated without saving the version. (PATCH /api/v2/agentic/virtualagents/{virtualAgentId}/versions/{versionId}) Requires permission agentic:virtualAgentVersion:edit. The id is the versionId. Required: id, virtual_agent_id, definition.
- **Create a Genesys Cloud agentic virtualagent** (Create). Create a virtual agent. (POST /api/v2/agentic/virtualagents) Requires permission agentic:virtualAgent:add. Required: name.
- **Get single Genesys Cloud agentic virtualagent by ID** (Get). Get virtual agent. (GET /api/v2/agentic/virtualagents/{virtualAgentId}) Requires permission agentic:virtualAgent:view. The id is the virtualAgentId. Required: id.
- **List all Genesys Cloud agentic virtualagents** (List). Get all virtual agents. (GET /api/v2/agentic/virtualagents) Requires permission agentic:virtualAgent:view. Pages automatically with pageNumber/pageSize.
- **Update a Genesys Cloud agentic virtualagent by ID** (Update). Update a virtual agent. (PATCH /api/v2/agentic/virtualagents/{virtualAgentId}) Requires permission agentic:virtualAgent:edit. The id is the virtualAgentId. Required: id, name.
- **Genesys Cloud alerting alert all bulk delete** (Delete). Delete all alerts for the user. (DELETE /api/v2/alerting/alerts/all) Requires permission alerting:alert:edit.
- **Genesys Cloud alerting alert all bulk partial update** (Update). Updates all alerts. (PATCH /api/v2/alerting/alerts/all) Requires permission alerting:alert:edit. Required: type.
- **Genesys Cloud alerting alert bulk bulk partial update** (Update). Bulk alert updates. (PATCH /api/v2/alerting/alerts/bulk) Requires permission alerting:alert:edit. Required: type, alertIds.
- **Delete a Genesys Cloud alerting alert by ID** (Delete). Delete an alert. (DELETE /api/v2/alerting/alerts/{alertId}) Requires permission alerting:alert:delete. The id is the alertId. Required: id.
- **Get single Genesys Cloud alerting alert by ID** (Get). Get an alert. (GET /api/v2/alerting/alerts/{alertId}) Requires permission alerting:alert:view. The id is the alertId. Required: id.
- **Genesys Cloud alerting alerts partial update** (Update). Allows an entity to mute/snooze an alert, update the unread status of the alert, or close an alert. Snoozing an alert temporarily stop it from resending notifications to individualsas well as other services within Genesys Cloud for a given period. Muting an alert will only block the notifications to individuals. Closing an alert will mark it as closed. (PATCH /api/v2/alerting/alerts/{alertId}) Requires permission alerting:alert:edit. Required: alert_id, type.
- **Genesys Cloud alerting alerts search** (Search). Gets a paged list of alerts. The max page size is 50. (POST /api/v2/alerting/alerts/query) Requires permission alerting:alert:view. Required: ruleType, queryType.
- **Update a Genesys Cloud alerting alert by ID** (Update). Update an alert read status. (PUT /api/v2/alerting/alerts/{alertId}) Requires permission alerting:alert:edit. The id is the alertId. Required: id, unread.
- **Genesys Cloud alerting rule bulk bulk partial update** (Update). Bulk update of notification lists. (PATCH /api/v2/alerting/rules/bulk) Requires permission alerting:rule:edit. Required: ruleIds.
- **Create a Genesys Cloud alerting rule bulk remove** (Create). Bulk remove rules. (POST /api/v2/alerting/rules/bulk/remove) Requires permission alerting:rule:delete. Required: ruleIds.
- **Create a Genesys Cloud alerting rule** (Create). Create a Rule. (POST /api/v2/alerting/rules) Requires permission alerting:rule:add. Required: name, type.
- **Delete a Genesys Cloud alerting rule by ID** (Delete). Delete a rule. (DELETE /api/v2/alerting/rules/{ruleId}) Requires permission alerting:rule:delete. The id is the ruleId. Required: id.
- **Get single Genesys Cloud alerting rule by ID** (Get). Get a rule. (GET /api/v2/alerting/rules/{ruleId}) Requires permission alerting:rule:view. The id is the ruleId. Required: id.
- **Genesys Cloud alerting rules search** (Search). Get a paged list of rules. The max size of the page is 50 items. (POST /api/v2/alerting/rules/query) Requires permission alerting:rule:view. Required: ruleType, queryType.
- **Update a Genesys Cloud alerting rule by ID** (Update). Update a rule. (PUT /api/v2/alerting/rules/{ruleId}) Requires permission alerting:rule:edit. The id is the ruleId. Required: id, name.
- **List all Genesys Cloud analytics action aggregate job results** (List). Fetch a page of results for an async aggregates query. (GET /api/v2/analytics/actions/aggregates/jobs/{jobId}/results) Requires any of permissions integrations:action:view, bridge:actions:view. Pages automatically: pass the returned next_cursor to get the next page. Required: job_id.
- **Create a Genesys Cloud analytics action aggregate job** (Create). Query for action aggregates asynchronously. (POST /api/v2/analytics/actions/aggregates/jobs) Requires any of permissions integrations:action:view, bridge:actions:view. Required: interval, metrics.
- **Delete a Genesys Cloud analytics action aggregate job by ID** (Delete). Delete/cancel an async request for action aggregates. (DELETE /api/v2/analytics/actions/aggregates/jobs/{jobId}) Requires any of permissions integrations:action:view, bridge:actions:view. The id is the jobId. Required: id.
- **Get single Genesys Cloud analytics action aggregate job by ID** (Get). Get status for async query for action aggregates. (GET /api/v2/analytics/actions/aggregates/jobs/{jobId}) Requires any of permissions integrations:action:view, bridge:actions:view. The id is the jobId. Required: id.
- **Genesys Cloud analytics action aggregates search** (Search). Query for action aggregates. (POST /api/v2/analytics/actions/aggregates/query) Requires any of permissions integrations:action:view, bridge:actions:view. Required: interval, metrics.
- **Genesys Cloud analytics agent status lookup** (Action). Get an agent and their active sessions by user ID. (GET /api/v2/analytics/agents/{userId}/status) Requires permission analytics:agentState:view. Required: user_id.
- **Genesys Cloud analytics agent status search** (Search). Retrieve the top 50 agents matching the query filters. (POST /api/v2/analytics/agents/status/query) Requires permission analytics:agentState:view.
- **Create a Genesys Cloud analytics agent status count** (Create). Count agents by different groupings. (POST /api/v2/analytics/agents/status/counts) Requires permission analytics:agentState:view.
- **List all analytics agentcopilot aggregate job results** (List). Fetch a page of results for an async aggregates query. (GET /api/v2/analytics/agentcopilots/aggregates/jobs/{jobId}/results) Requires permission analytics:agentCopilotAggregate:view. Pages automatically: pass the returned next_cursor to get the next page. Required: job_id.
- **Create a Genesys Cloud analytics agentcopilot aggregate job** (Create). Query for agent copilot aggregates asynchronously. (POST /api/v2/analytics/agentcopilots/aggregates/jobs) Requires permission analytics:agentCopilotAggregate:view. Required: interval, metrics.
- **Delete a Genesys Cloud analytics agentcopilot aggregate job by ID** (Delete). Delete/cancel an async request for agent copilot aggregates. (DELETE /api/v2/analytics/agentcopilots/aggregates/jobs/{jobId}) Requires permission analytics:agentCopilotAggregate:view. The id is the jobId. Required: id.
- **Get analytics agentcopilot aggregate job by ID** (Get). Get status for async query for agent copilot aggregates. (GET /api/v2/analytics/agentcopilots/aggregates/jobs/{jobId}) Requires permission analytics:agentCopilotAggregate:view. The id is the jobId. Required: id.
- **Genesys Cloud analytics agentcopilot aggregates search** (Search). Query for agent copilot aggregates. (POST /api/v2/analytics/agentcopilots/aggregates/query) Requires permission analytics:agentCopilotAggregate:view. Required: interval, metrics.
- **List all Genesys Cloud analytics bot aggregate job results** (List). Fetch a page of results for an async aggregates query. (GET /api/v2/analytics/bots/aggregates/jobs/{jobId}/results) Requires permission analytics:botAggregate:view. Pages automatically: pass the returned next_cursor to get the next page. Required: job_id.
- **Create a Genesys Cloud analytics bot aggregate job** (Create). Query for bot aggregates asynchronously. (POST /api/v2/analytics/bots/aggregates/jobs) Requires permission analytics:botAggregate:view. Required: interval, metrics.
- **Delete a Genesys Cloud analytics bot aggregate job by ID** (Delete). Delete/cancel an async request for bot aggregates. (DELETE /api/v2/analytics/bots/aggregates/jobs/{jobId}) Requires permission analytics:botAggregate:view. The id is the jobId. Required: id.
- **Get single Genesys Cloud analytics bot aggregate job by ID** (Get). Get status for async query for bot aggregates. (GET /api/v2/analytics/bots/aggregates/jobs/{jobId}) Requires permission analytics:botAggregate:view. The id is the jobId. Required: id.
- **Genesys Cloud analytics bot aggregates search** (Search). Query for bot aggregates. (POST /api/v2/analytics/bots/aggregates/query) Requires permission analytics:botAggregate:view. Required: interval, metrics.
- **List all Genesys Cloud analytics botflow division reportingturns** (List). Get Reporting Turns (division aware). Returns the reporting turns for the specified flow, filtered by the clients divisions and grouped by session, in reverse chronological order from the date the session was created, with the reporting turns from the most recent session appearing at the start of the list. (GET /api/v2/analytics/botflows/{botFlowId}/divisions/reportingturns) Requires permission analytics:botFlowDivisionAwareReportingTurn:view. Pages automatically: pass the returned next_cursor to get the next page. Required: bot_flow_id.
- **List all Genesys Cloud analytics botflow sessions** (List). Get Bot Flow Sessions. Returns the bot flow sessions in reverse chronological order from the date they were created. It is expected that the client will URL encode the request URI once only. (GET /api/v2/analytics/botflows/{botFlowId}/sessions) Requires permission analytics:botFlowSession:view. Pages automatically: pass the returned next_cursor to get the next page. Required: bot_flow_id.
- **List all analytics casemanagement aggregate job results** (List). Fetch a page of results for an async case management query. (GET /api/v2/analytics/casemanagement/aggregates/jobs/{jobId}/results) Requires permission analytics:caseManagementAggregate:view. Pages automatically: pass the returned next_cursor to get the next page. Required: job_id.
- **Create a Genesys Cloud analytics casemanagement aggregate job** (Create). Query for case management aggregates asynchronously. (POST /api/v2/analytics/casemanagement/aggregates/jobs) Requires permission analytics:caseManagementAggregate:view. Required: interval, metrics.
- **Delete analytics casemanagement aggregate job by ID** (Delete). Delete/cancel an async request for case management aggregates. (DELETE /api/v2/analytics/casemanagement/aggregates/jobs/{jobId}) Requires permission analytics:caseManagementAggregate:view. The id is the jobId. Required: id.
- **Get analytics casemanagement aggregate job by ID** (Get). Get status for async query for case management aggregates. (GET /api/v2/analytics/casemanagement/aggregates/jobs/{jobId}) Requires permission analytics:caseManagementAggregate:view. The id is the jobId. Required: id.
- ...and 3091 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
