Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Solutif Genesys Cloud MCP Server Search for queues named 'support' and show their conversation volumes."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Solutif's MCP server for Genesys Cloud Platform API operations and analytics.
Tool | Description |
Creates a queue after checking for a duplicate name | |
Searches queues by name | |
Retrieves queue conversation volumes | |
Samples conversations from a queue | |
Retrieves voice quality metrics | |
Retrieves conversation sentiment | |
Retrieves conversation topics | |
Searches voice conversations | |
Retrieves a conversation transcript | |
Lists OAuth clients | |
Retrieves OAuth client usage |
Related MCP server: Genesys Cloud MCP Server
npm install
npm run buildConfigure your MCP client to run the local build:
{
"mcpServers": {
"solutif-genesys-cloud": {
"command": "node",
"args": ["/absolute/path/to/genesys-cloud-mcp-server/dist/index.js"],
"env": {
"GENESYSCLOUD_REGION": "<REGION>",
"GENESYSCLOUD_OAUTHCLIENT_ID": "<OAUTH_CLIENT_ID>",
"GENESYSCLOUD_OAUTHCLIENT_SECRET": "<OAUTH_CLIENT_SECRET>"
}
}
}
}The server is read-only by default. To expose create_queue, add:
"GENESYSCLOUD_ENABLE_QUEUE_CREATION": "true"The OAuth client then needs routing:queue:add and routing:queue:view. Keep create_queue out of the MCP client's auto-approved tools so every write requires user approval.
npm run package:mcpbInstall the generated genesys-cloud-mcp-server.mcpb in Claude Desktop. Queue creation is disabled by default and can be enabled in the extension settings.
npm run lint:check
npm run build
npm test -- --runBased on the MIT-licensed MakingChatbots Genesys Cloud MCP Server.
Retrieves sentiment analysis scores for one or more conversations. Sentiment is evaluated based on customer phrases, categorized as positive, neutral, or negative. The result includes both a numeric sentiment score (-100 to 100) and an interpreted sentiment label.
Inputs: conversationIds (required).
Retrieves Speech and Text Analytics topics detected for a specific conversation. Topics represent business-level intents (e.g. cancellation, billing enquiry) inferred from recognised phrases in the customer-agent interaction.
Inputs: conversationId (required).
Retrieves a structured transcript of the conversation, including speaker labels, utterance timestamps, and sentiment annotations where available. The transcript is formatted as a time-aligned list of utterances attributed to each participant (e.g., customer or agent)
Inputs: conversationId (required).
Retrieves a list of all OAuth clients, including their associated roles and divisions. This tool is useful for auditing and managing OAuth clients in the Genesys Cloud organization.
Inputs: no named parameters.
Retrieves the usage of an OAuth Client for a given period. It returns the total number of requests and a breakdown of Platform API endpoints used by the client.
Inputs: endDate (required), startDate (required), oauthClientId (required).
Returns a breakdown of how many conversations occurred in each specified queue between two dates. Useful for comparing workload across queues. MAX 300 queue IDs.
Inputs: endDate (required), queueIds (required), startDate (required).
Retrieves conversation analytics for a specific queue between two dates, returning a representative sample of conversation IDs. Useful for reporting, investigation, or summarisation.
Inputs: endDate (required), queueId (required), startDate (required).
Searches for routing queues based on their name, allowing for wildcard searches. Returns a paginated list of matching queues, including their Name, ID, Description (if available), and Member Count (if available). Also provides pagination details like current page, page size, total results found, and total pages available. Useful for finding specific queue IDs, checking queue configurations, or listing available queues.
Inputs: name (required), pageSize, pageNumber.
Searches for voice conversations within a specified time window, optionally filtering by phone number. Returns a paginated list of conversation IDs and call duration for use in further analysis or tool calls.
Inputs: endDate (required), startDate (required), pageSize, pageNumber, +1 more.
Retrieves voice call quality metrics for one or more conversations by ID. This tool specifically focuses on voice interactions and returns the minimum Mean Opinion Score (MOS) observed in each conversation as structured JSON. MOS is a measure of perceived audio quality based on factors such as jitter, latency, packet loss, and codec. Use the following legend to interpret MOS values:
• Poor: MOS < 3.5 • Acceptable: 3.5 ≤ MOS < 4.3 • Excellent: MOS ≥ 4.3
Inputs: conversationIds (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Most tools have clearly distinct outputs: transcript, sentiment scores, topics, voice quality, queue volumes, and OAuth usage are separable. A minor overlap exists between conversation_transcript (which can include sentiment annotations) and conversation_sentiment, and between the two conversation-ID discovery tools, but descriptions are enough to resolve this.
The set mixes verb-led names like search_queues and query_queue_volumes with noun-phrase names like conversation_transcript, voice_call_quality, and oauth_clients. The naming is readable and mostly snake_case, but the absent verb pattern prevents strong consistency.
Ten tools is a well-scoped size for a Genesys Cloud server covering conversation analytics, queue interrogation, and OAuth auditing. Each tool has a distinct responsibility and none feel redundant.
Conversation-centric workflows are well covered: discovery, sampling, transcript, sentiment, topics, and call quality are all present. Minor gaps like the lack of non-voice conversation search and OAuth client management actions prevent a perfect score.
Reporting, callback operations, queue settings and Custom IVR flows for RingCentral call queues.
Manage API keys, identities, permissions, rate-limit overrides and verification analytics.
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
CX ops: read conversations, calls and QA evaluations from Zendesk, Freshdesk, Five9 and more.
