Skip to main content
Glama
deenesjakoruzh
m-7-m

Genesys Flow MCP

by m-7-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Genesys Flow MCP

Servidor MCP local que se conecta a Genesys Cloud, lista rutas de IVR, recupera el flujo de horario de apertura configurado de un IVR y genera documentación Markdown legible.

El documento generado está estructurado tanto para lectores técnicos como de negocio:

  • Ruta — nombre del IVR, ID, estado, DNIS (cuando esté disponible) y flujo configurado.

  • Enfoque de negocio — el propósito del flujo y el enrutamiento del menú del cliente.

  • Enfoque técnico — configuración del flujo, variables, prompts/TTS, tareas, menús y rutas de decisión.

  • Integraciones y dependencias de enrutamiento — Data Actions, Bot Flows y colas ACD.

Requisitos previos

  • Node.js 18 o posterior

  • Un cliente OAuth de Genesys Cloud que use el flujo de Client Credentials

  • Permisos para leer IVRs y flujos de Architect en la organización de Genesys Cloud correspondiente

Related MCP server: Hive Mind MCP Server

Instalar y configurar

Instala las dependencias:

cd <path-to-genesys-flow-mcp>
npm install

Crea un archivo .env en la raíz del proyecto:

GENESYS_CLIENT_ID=your-client-id
GENESYS_CLIENT_SECERET=your-client-secret
GENESYS_REGION=ie

Importante: GENESYS_CLIENT_SECERET está escrito así a propósito porque coincide con el código fuente actual. No lo renombres a SECRET a menos que también actualices src/config/env.ts.

Establece GENESYS_REGION al sufijo de tu región de Genesys Cloud, por ejemplo ie para mypurecloud.ie.

Ejecutar localmente

Para desarrollo:

npm run dev

Para el servidor compilado usado por clientes de escritorio:

npm run build
npm start

El servidor usa el transporte stdio de MCP. Lo inicia el cliente MCP; no expone una URL de navegador ni un puerto HTTP.

Probar con MCP Inspector

Usa MCP Inspector para probar el servidor directamente antes de conectarlo a Claude Desktop:

cd <path-to-genesys-flow-mcp>
npm run inspect

El Inspector abre una interfaz de navegador local. En ella:

  1. Conéctate al servidor usando la configuración stdio predeterminada.

  2. Abre la pestaña Tools.

  3. Ejecuta get_ivrs para confirmar la autenticación de Genesys y la recuperación de rutas.

  4. Ejecuta get_flow_by_name con un nombre de IVR, por ejemplo:

    {
  "name": "testt call"
}

  5. Comprueba que la respuesta comienza con la sección Route e incluye el flujo configurado, los prompts y las integraciones.

Herramientas disponibles

get_ivrs

Devuelve la lista de enrutamiento/IVR de Genesys Cloud.

Ejemplo de solicitud:

List the available Genesys IVRs.

get_flow_by_name

Busca un IVR por nombre, recupera su flujo de horario de apertura configurado y devuelve documentación Markdown.

Entrada:

{
  "name": "testt call"
}

Ejemplo de solicitud:

Use get_flow_by_name for the IVR named "testt call".

Si no se encuentra el IVR, o no tiene flujo de horario de apertura, la herramienta devuelve un error que describe el problema.

Qué incluye la documentación generada

La documentación sigue la relación siguiente:

Genesys IVR Route
        ↓
Configured Open-Hours Flow
        ├── Business Focus: customer routing and menu choices
        └── Technical Focus: prompts, variables, tasks, menus, integrations

La detección de integraciones cubre las dependencias comunes de Architect que se indican a continuación:

Elemento de Architect

Documentado como

DataAction

Data Action / Web Services Data Action

CallBotFlowAction

Bot Flow, incluidos nombre e ID del flujo

TransferPureMatchAction

Cola ACD

Todos los prompts TTS encontrados en tareas y saludos de menú se incluyen en el recorrido técnico del flujo.

Probar con Claude Desktop

  1. Compila el proyecto:

    cd <path-to-genesys-flow-mcp>
npm run build

  2. En Claude Desktop, abre:

    File → Settings → Developer → Edit Config

  3. Añade lo siguiente en el nivel superior del archivo JSON abierto. Conserva cualquier configuración existente, como preferences.

    {
  "mcpServers": {
    "genesys-flow": {
      "command": "node",
      "args": [
        "<path-to-genesys-flow-mcp>\\dist\\index.js"
      ],
      "env": {
        "GENESYS_CLIENT_ID": "your-client-id",
        "GENESYS_CLIENT_SECERET": "your-client-secret",
        "GENESYS_REGION": "ie"
      }
    }
  }
}

    Reemplaza <path-to-genesys-flow-mcp> con la ruta completa a tu carpeta de proyecto local. Si el archivo ya contiene propiedades, añade mcpServers junto a ellas y asegúrate de que la propiedad anterior termine con una coma.

  4. Cierra y vuelve a abrir Claude Desktop por completo.

  5. Inicia un nuevo chat y pregunta:

    What Genesys tools are available?

    Luego prueba la documentación:

    Use get_flow_by_name for the IVR named "testt call" and document its route, configured flow, prompts, and integrations.

No confirmes ni compartas la configuración de Claude Desktop si contiene tu secreto de cliente. Para una prueba local en un dispositivo personal, es aceptable pasar las credenciales a través del bloque env de MCP. Usa un cliente OAuth dedicado con los permisos mínimos requeridos de Genesys.

Verificación de compilación

Ejecuta la verificación de compilación de TypeScript después de los cambios de código:

npm run build

Estructura del proyecto

src/
├── config/       Environment variable validation
├── mcp/          MCP server and tool registration
├── services/     Genesys authentication, API access, and documentation generation
├── tools/        MCP tool handlers
└── types/        Genesys Cloud response types

Available Tools

2 tools
get_flow_by_nameB

Get a documented Genesys flow by IVR name.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesIVR name

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It only states the action (get by name) and adds the adjective 'documented' as a constraint, but does not disclose output format, error behavior, authentication needs, or whether the operation is safe/read-only. Minimal behavioral context beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with the verb and resource clearly stated. No filler or redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter lookup tool, the description covers the core purpose. However, with no output schema, it omits return value details (what a 'documented flow' looks like) and does not disambiguate from the sibling tool. Adequate but with notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with the 'name' parameter described as 'IVR name'. The description repeats this same context, adding no new meaning beyond the schema. Baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'documented Genesys flow' with a clear lookup scope ('by IVR name'). It effectively distinguishes itself from the sibling tool 'get_ivrs' by targeting flows rather than IVR lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives are provided. The sibling tool 'get_ivrs' is not mentioned, and the description does not clarify when to choose this over getting IVRs. Guidance is only implicit via the IVR name parameter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_ivrsA

Get all available IVRs from Genesys Cloud.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description does not disclose any behavioral aspects such as permissions, side effects, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no superfluous words, perfectly sized for its simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description adequately conveys that the tool returns all available IVRs, satisfying the need for a simple list retrieval.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the description fully covers the input schema; no additional explanation needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'all available IVRs', distinct from the sibling tool 'get_flow_by_name' which targets flows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives; usage is implied as the go-to for fetching all IVRs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedget_flow_by_name
    • First observedget_ivrs
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation4/5

The two tools are distinct: one retrieves IVRs, the other retrieves a flow by name. However, the second tool's description is unclear about what 'documented' means and how it relates to the IVR name, which could cause slight confusion.

Naming Consistency4/5

Both tools follow the get_ pattern with noun complements (ivrs, flow_by_name). The naming is mostly consistent but 'flow_by_name' includes a qualifier that 'ivrs' lacks, a minor deviation.

Tool Count3/5

With only two tools, the server covers a very narrow scope. While this may be appropriate for a minimal integration, it feels thin and may not justify a dedicated server.

Completeness2/5

The domain appears to be IVR and flow management, but only retrieval operations are present. Missing operations like creating, updating, or deleting flows/IVRs are significant gaps, leaving the surface incomplete.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Related MCP Connectors

Related MCP Servers

  • Hive Mind MCP Server

    Jahanzaib-Kaleem
    A
    license
    Not graded
    quality
    D
    maintenance
    Automatically generates and maintains living documentation for codebases by creating hierarchical hivemind.md files and flowchart diagrams at every directory level, enabling AI navigation and real-time or retroactive documentation of code structure, requirements, and dependencies.
    MIT

  • Documentation MCP Server

    esola-thomas
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to navigate and query hierarchical documentation structures, supporting markdown files with YAML metadata and OpenAPI 3.x specifications. It features intelligent full-text search, metadata filtering, and a built-in web interface for both human and AI-driven documentation access.
    6
    MIT