AYX-MCP-Wrapper
Related Servers
Alternatives to AYX-MCP-Wrapper
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA versatile Model Context Protocol server that enables AI assistants to manage calendars, track tasks, handle emails, search the web, and control smart home devices.23-
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with N8N workflows, executions, and automation capabilities.12MIT
- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.4 npm11MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with n8n workflows through natural language, supporting actions like listing, creating, updating, executing and monitoring workflows.281 npm1,633MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants and development tools to interact with ServiceNow instances, providing comprehensive API coverage for incident management, change management, CMDB, and other ServiceNow modules.3MIT
TDQS
Scored across 43 tools
Most tools have distinct purposes targeting specific resources (e.g., collections, schedules, workflows, users) and actions (e.g., get, create, update, delete), with clear boundaries. However, some overlap exists, such as 'execute_workflow_with_monitoring' and 'start_workflow_execution' potentially causing confusion, and multiple 'get_user_by_*' tools for different lookup methods, though descriptions help clarify.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Examples include 'activate_schedule', 'create_collection', 'get_all_users', and 'update_user_details', with no deviations in style or convention, making them predictable and readable.
With 43 tools, the count is excessive for the server's purpose of wrapping Alteryx functionality, leading to a heavy and potentially overwhelming interface. A more focused set of 15-25 tools would better serve the domain without sacrificing coverage, as many operations could be consolidated or streamlined.
The tool set provides comprehensive coverage for managing Alteryx server resources, including full CRUD/lifecycle operations for collections, schedules, workflows, and users, along with execution, monitoring, and asset management. No obvious gaps are present, ensuring agents can handle end-to-end workflows without dead ends.