F
licenseNot graded
qualityB
maintenanceCaptures Genesys Cloud Architect flows and their dependent resources, then generates grounded business and technical documentation as Markdown, PDF, and diagrams from immutable capture bundles.
-
Genesys Flow MCP
by m-7-m
Related Servers
Alternatives to Genesys Flow MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAnalyzes code repositories and generates comprehensive documentation published to Google Docs with Mermaid diagrams.12MIT
- FlicenseNot gradedqualityDmaintenanceAutomatically generates comprehensive wiki documentation from any codebase, including Mermaid diagrams, source code citations, and automated quality checks.2-
- AlicenseNot gradedqualityDmaintenanceAutomatically 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
- -licenseBqualityNot gradedmaintenanceAutomates the creation of standardized documentation by extracting information from source files and applying templates, with integration capabilities for GitHub, Google Drive, and Perplexity AI.33-
- AlicenseAqualityCmaintenanceEnables 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.6MIT
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