Genesys Cloud - Developer Community!

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

Amazing work @Lawrence Drayton! You've got a load of really useful tools.

Do you interact with the metrics using Claude Code, or the Claude Desktop App? I'd love to see what these metrics like these looked like with Claude's Interactive Charts, produced by the latter.

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

Thank you@Lucas Woodward

once connected it will work in either code or regular chat, basically wherever you wire it in (though I haven't personally tested it, but have had other users tell me it's worked)

I have had it do complete agent reviews and asked it to produce fully formatted documents for distribution to the leaders in the team. I haven't tried any interactive charts yet but keen to try that tomorrow now! 

next update to the mcp js being pushed tomorrow with more tools and refinements.

Great to connect! I actually use your platform-api skill and suggest its use as part of this mcp! 

Amazing work @Lawrence Drayton! You've got a load of really useful tools.

Do you interact with the metrics using Claude Code, or the Claude Desktop App? I'd love to see what these metrics like these looked like with Claude's Interactive Charts, produced by the latter.

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

The interactive charts always look really whizzy. Please do share screenshots of what it produces with this data, I'd love to see them.

I love the idea of using it with Claude Code specifically (as you say it works with all other clients though). Claude Code is so easy to allow you to quickly iterate on reports, or even answer emails with relevant metrics automatically - its got a great ecosystem. It's a brave new world!

Thank you for linking to my Platform API skill. It's addictive creating these things!

------------------------------
Lucas Woodward
Winner of Orchestrator of the Year, Developer (2025)

LinkedIn - https://www.linkedin.com/in/lucas-woodward-the-dev
Newsletter - https://makingchatbots.com

Original Message:
Sent: 05-01-2026 07:24
From: Lawrence Drayton
Subject: genesys-mcp: Open-source MCP bridge for Claude Code (Or any LLM, really)→ Genesys Cloud

Thank you@Lucas Woodward

once connected it will work in either code or regular chat, basically wherever you wire it in (though I haven't personally tested it, but have had other users tell me it's worked)

I have had it do complete agent reviews and asked it to produce fully formatted documents for distribution to the leaders in the team. I haven't tried any interactive charts yet but keen to try that tomorrow now! 

next update to the mcp js being pushed tomorrow with more tools and refinements.

Great to connect! I actually use your platform-api skill and suggest its use as part of this mcp! 

------------------------------
Lawrence Drayton
Consultant

Original Message:
Sent: 05-01-2026 07:16
From: Lucas Woodward
Subject: genesys-mcp: Open-source MCP bridge for Claude Code (Or any LLM, really)→ Genesys Cloud

Amazing work @Lawrence Drayton! You've got a load of really useful tools.

Do you interact with the metrics using Claude Code, or the Claude Desktop App? I'd love to see what these metrics like these looked like with Claude's Interactive Charts, produced by the latter.

------------------------------
Lucas Woodward
Winner of Orchestrator of the Year, Developer (2025)

LinkedIn - https://www.linkedin.com/in/lucas-woodward-the-dev
Newsletter - https://makingchatbots.com

Original Message:
Sent: 04-29-2026 19:25
From: Lawrence Drayton
Subject: genesys-mcp: Open-source MCP bridge for Claude Code (Or any LLM, really)→ Genesys Cloud

Hey all! 

Posted this over in the general community but might be better here!

I've open-sourced an MCP server I built for my own contact-centre ops work and it's been valuable enough that I figured the wider Genesys community might want it. Sharing here for feedback and to invite contributors.

Repo: https://github.com/laggyzee/genesys-mcp Licence: MIT

What is it

genesys-mcp is a local stdio Model Context Protocol server that exposes a curated, read-only set of Genesys Cloud tools to MCP-compatible AI clients (Claude Code, Cursor, Continue, etc.). Once installed, you can ask the LLM things like:

• "Pull last week's abandon rate by queue"
• "What's the live wallboard look like for these queues?"
• "Find all customers who called us 3+ times this week"
• "Did anyone go over their break or lunch this week?"
• "Pull a quality snapshot for agent X compared to peers"
• "What's the EWT on the Sales queue right now?"

…and the LLM picks the right Genesys API endpoints, makes the calls, and writes up the answer. Everything is read-only - the OAuth client uses Client Credentials with *:readonly scopes, so there's no write surface even via the escape hatch.

It's been replacing a lot of the "log into Admin → run a report → paste numbers into a spreadsheet" loop that ops teams do every day.

How it works

• Python (FastMCP) server running locally over stdio
• Official PureCloudPlatformClientV2 SDK for typed API access
• Generic call_genesys_api escape hatch for endpoints not yet wrapped, with auto 401 retry
• Internal id → name cache (queues, users, wrap-up codes) so most responses come back human-readable
• Multi-region - Sydney, Virginia, Ireland out of the box; trivial to add others

Tool surface

About 35 tools across these areas:

• Directory - list/search queues, users, skills, wrap-up codes; per-user routing status & live presence
• Real-time analytics - queue_observation, queue_estimated_wait_time (the AI-adjusted-AHT model), queue_performance with derived answered/abandoned/service_level_pct fields that match the Performance UI columns
• Conversations - search, full detail, recording metadata, signed media-download URLs
• Presence sessions - break/meal/away analysis wrapping the analytics/users/details async-jobs flow into a single call
• Composition reports - repeat_caller_report, break_overrun_report, agent_quality_snapshot, live_wallboard (each chains 2–4 endpoints into ops-ready output)
• Speech & text analytics (needs speech-and-text-analytics:readonly) - conversation summaries, sentiment, transcript URLs
• External contacts (needs external-contacts:readonly) - phone/email → CRM record lookup
• Workforce management (needs workforce-management:readonly) - management-unit topology, agent adherence explanations, combined adherence-vs-presence review
• call_genesys_api - generic escape hatch for any /api/v2/* endpoint

Full table in the README.

Setup (5-min install)

# 1. Clonegit clone https://github.com/laggyzee/genesys-mcpcd genesys-mcp# 2. Create an OAuth Client Credentials client in Genesys Admin#    Required scopes: analytics:readonly, conversations:readonly,#    recordings:readonly, users:readonly, routing:readonly#    Optional: speech-and-text-analytics:readonly, external-contacts:readonly,#    workforce-management:readonly# 3. Set env varscp .env.example ~/.config/genesys-mcp.envchmod 600 ~/.config/genesys-mcp.env# edit and paste your client_id, client_secret, region# 4. Install depsuv sync   # or: pip install -e .# 5. Wire into your MCP client

For Claude Code, add to ~/.claude/mcp.json:

{  "mcpServers": {    "genesys": {      "command": "uv",      "args": ["run", "--directory", "/path/to/genesys-mcp", "python", "-m", "genesys_mcp.server"],      "env": {        "GENESYS_CLIENT_ID": "...",        "GENESYS_CLIENT_SECRET": "...",        "GENESYS_REGION": "ap-southeast-2"      }    }  }}

Restart Claude Code and you're done.

Example sessions

A few real prompts I've used this week:

Things on the roadmap (PRs welcome)

• Web messaging transcript wrapper (the /api/v2/conversations/messages/{id}/messages/bulk flow currently needs the escape hatch)
• Full async historical adherence (scheduled vs. actual percentages with shift overlay)
• Quality evaluations / scorecards (quality:readonly)
• Outbound campaign progress (outbound:readonly)

Why share?

Building this saved me probably 5–10 hours a week on routine ops reporting and made it possible to answer things like "show me agents whose wrap-up note discipline dropped this week" in one prompt instead of an afternoon of clicking. If anyone in this community gets the same lift out of it, that's worth more than me keeping it private.

Happy to take questions, PRs, or feedback.

Repo: https://github.com/laggyzee/genesys-mcp

Security note: The OAuth client credentials in this setup connect your MCP server to your tenant. The server runs locally on your machine and stores credentials only in your env vars or a local gitignored .env. Nothing leaves your machine apart from the API calls Claude makes to Genesys on your behalf. Use a dedicated read-only OAuth role per the README - don't reuse a high-privilege client.

#Integrations
#PlatformAPI
#PlatformCLI
#PlatformSDK

------------------------------
Lawrence Drayton
Consultant
------------------------------