Skip to main content
Glama
deenesjakoruzh
m-7-m

Genesys Flow MCP

by m-7-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Genesys Flow MCP

Lokaler MCP-Server, der eine Verbindung zu Genesys Cloud herstellt, IVR-Routen auflistet, den konfigurierten Open-Hours-Flow einer IVR abruft und lesbare Markdown-Dokumentation erzeugt.

Das generierte Dokument ist sowohl für geschäftliche als auch für technische Leser strukturiert:

  • Route — IVR-Name, ID, Status, DNIS (sofern verfügbar) und konfigurierter Flow.

  • Business-Fokus — der Flow-Zweck und das Kundenmenü-Routing.

  • Technischer Fokus — Flow-Einstellungen, Variablen, Prompts/TTS, Tasks, Menüs und Entscheidungspfade.

  • Integrationen und Routing-Abhängigkeiten — Data Actions, Bot Flows und ACD-Warteschlangen.

Voraussetzungen

  • Node.js 18 oder neuer

  • Ein Genesys Cloud OAuth-Client mit dem Client Credentials-Grant

  • Berechtigungen zum Lesen von Architect-IVRs und -Flows in der relevanten Genesys-Cloud-Organisation

Related MCP server: Hive Mind MCP Server

Installation und Konfiguration

Abhängigkeiten installieren:

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

Erstellen Sie eine .env-Datei im Projektstamm:

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

Wichtig: GENESYS_CLIENT_SECERET ist absichtlich so geschrieben, weil es dem aktuellen Quellcode entspricht. Benennen Sie es nicht in SECRET um, es sei denn, Sie aktualisieren auch src/config/env.ts.

Setzen Sie GENESYS_REGION auf das Suffix Ihrer Genesys-Cloud-Region, z. B. ie für mypurecloud.ie.

Lokal ausführen

Für die Entwicklung:

npm run dev

Für den kompilierten Server, der von Desktop-Clients verwendet wird:

npm run build
npm start

Der Server verwendet den MCP-stdio-Transport. Er wird vom MCP-Client gestartet; er stellt keine Browser-URL oder HTTP-Port bereit.

Mit MCP Inspector testen

Verwenden Sie den MCP Inspector, um den Server direkt zu testen, bevor Sie ihn mit Claude Desktop verbinden:

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

Der Inspector öffnet eine lokale Browser-Oberfläche. Darin:

  1. Verbinden Sie sich mit dem Server über die Standard-stdio-Konfiguration.

  2. Öffnen Sie den Tab Tools.

  3. Führen Sie get_ivrs aus, um die Genesys-Authentifizierung und den Routenabruf zu bestätigen.

  4. Führen Sie get_flow_by_name mit einem IVR-Namen aus, zum Beispiel:

    {
  "name": "testt call"
}

  5. Prüfen Sie, dass die Antwort mit dem Abschnitt Route beginnt und den konfigurierten Flow, Prompts und Integrationen enthält.

Verfügbare Tools

get_ivrs

Gibt die Genesys-Cloud-Routing-/IVR-Liste zurück.

Beispielanfrage:

List the available Genesys IVRs.

get_flow_by_name

Sucht eine IVR anhand des Namens, ruft ihren konfigurierten Open-Hours-Flow ab und gibt Markdown-Dokumentation zurück.

Eingabe:

{
  "name": "testt call"
}

Beispielanfrage:

Use get_flow_by_name for the IVR named "testt call".

Wenn die IVR nicht gefunden wird oder keinen Open-Hours-Flow hat, gibt das Tool einen Fehler zurück, der das Problem beschreibt.

Was die generierte Dokumentation enthält

Die Dokumentation folgt der folgenden Beziehung:

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

Die Integrationserkennung deckt die folgenden gängigen Architect-Abhängigkeiten ab:

Architect-Element

Dokumentiert als

DataAction

Data Action / Web Services Data Action

CallBotFlowAction

Bot Flow, einschließlich Name und Flow-ID

TransferPureMatchAction

ACD-Warteschlange

Alle TTS-Prompts, die in Tasks und Menü-Begrüßungen gefunden werden, sind im technischen Flow-Durchlauf enthalten.

Mit Claude Desktop testen

  1. Projekt erstellen:

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

  2. In Claude Desktop öffnen:

    File → Settings → Developer → Edit Config

  3. Fügen Sie Folgendes auf der obersten Ebene der geöffneten JSON-Datei hinzu. Bewahren Sie vorhandene Einstellungen wie preferences auf.

    {
  "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"
      }
    }
  }
}

    Ersetzen Sie <path-to-genesys-flow-mcp> durch den vollständigen Pfad zu Ihrem lokalen Projektordner. Wenn die Datei bereits Eigenschaften enthält, fügen Sie mcpServers daneben hinzu und stellen Sie sicher, dass die vorherige Eigenschaft mit einem Komma endet.

  4. Beenden Sie Claude Desktop vollständig und öffnen Sie es erneut.

  5. Starten Sie einen neuen Chat und fragen Sie:

    What Genesys tools are available?

    Testen Sie dann die Dokumentation:

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

Geben Sie die Claude-Desktop-Konfiguration nicht weiter, wenn sie Ihr Client-Secret enthält. Für einen lokalen Test auf einem persönlichen Gerät ist die Übergabe der Anmeldedaten über den MCP-env-Block akzeptabel. Verwenden Sie einen dedizierten OAuth-Client mit den minimal erforderlichen Genesys-Berechtigungen.

Build-Prüfung

Führen Sie nach Codeänderungen die TypeScript-Build-Prüfung aus:

npm run build

Projektstruktur

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