Amazon Connect MCP Server
Related Servers
Alternatives to Amazon Connect MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to Five9 cloud contact center, enabling management of campaigns, agents, IVR flows, and reports through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to Five9 contact centers, enabling natural language management of IVR flows, campaigns, agents, and real-time statistics.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server connecting AI assistants to the Five9 contact center, enabling management of campaigns, agents, IVR flows, and reports via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that connects AI assistants to Five9 contact center, allowing management of campaigns, agents, lists, and statistics via natural language commands.16MIT
- AlicenseAqualityCmaintenanceMCP server enabling AI assistants to interact with your LogicMonitor, providing 125 tools for comprehensive monitoring and management operations.7095 npm13AGPL 3.0
- AlicenseCqualityCmaintenanceA unified MCP server for AWS that enables natural language infrastructure management, cross-service resource discovery, and dependency mapping. It features 30 intelligent tools for cost optimization, incident investigation, and multi-account operations protected by a robust safety system.305MIT
TDQS
Scored across 107 tools
Many tools overlap in purpose and naming. For example, search_cases and cases_list_cases_for_contact both retrieve cases, ai_search_quick_responses and ai_list_quick_responses overlap, and template_customize, template_get_case_workflow, and template_get_routing_workflow create confusion. Several domains (cases, profiles, AI, templates) have similar list/get/create patterns that can be hard to distinguish.
Naming is inconsistent: some tools use resource_prefix_verb (cases_list_templates, profiles_create_profile), others use verb_noun (list_queues, describe_contact, create_instance), and a few use noun_verb (template_customize, layout_visualizer). There is also mixed terminology like cases_update_field vs config_update_queue_status vs profiles_merge.
107 tools is far beyond typical MCP server scope and creates a massive surface for an agent to evaluate. While the server covers many Connect services, the count is excessive and will cause decision overhead and hallucination risk.
The server covers an impressive breadth of Connect features: instances, cases, contacts, configuration, analytics, profiles, campaigns, AI, and templates. Minor gaps exist (e.g., no explicit delete for queues, contact flows, or phone numbers, and no update for hours of operation), but the core lifecycle is largely covered.