AYX-MCP-Wrapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_collectionsB | Get the list of all collections of the Alteryx server |
| get_collection_by_idC | Get a collection by its ID |
| create_collectionC | Create a new collection |
| delete_collectionC | Delete a collection by its ID |
| update_collection_name_or_ownerC | Update a collection name or owner by its ID |
| add_workflow_to_collectionC | Add a workflow to a collection by its ID |
| remove_workflow_from_collectionC | Remove a workflow from a collection by its ID |
| add_schedule_to_collectionC | Add a schedule to a collection by its ID |
| remove_schedule_from_collectionC | Remove a schedule from a collection by its ID |
| get_all_workflowsB | Get the list of all workflows of the Alteryx server |
| get_workflow_by_idC | Get a workflow by its ID |
| update_workflow_name_or_commentC | Update a workflow name or comment by its ID |
| download_workflow_package_fileC | Download a workflow package file by its ID and save it to the local directory |
| get_workflow_xmlC | Get the XML representation of a workflow file by its ID |
| get_workflow_tool_listC | Get the list of tools in a workflow by the workflow ID |
| transfer_workflowC | Transfer workflow ownership to a new user |
| get_workflow_jobsC | Get all jobs associated with a workflow |
| start_workflow_executionC | Start a workflow execution by its ID and return the job ID. This will create a new job and add it to the execution queue. This call will return a job ID that can be used to get the job details later. The input data is a list of name-value pairs, each containing a name and value. |
| execute_workflow_with_monitoringC | Execute a workflow by its ID and monitor its execution status. This call will return a jobID, he Job status and the job details once the execution is completed or failed. The input data parameter is a list of name-value pairs, each containing a name and value. |
| get_all_usersB | Get the list of all users of the Alteryx server |
| get_user_by_idC | Get a user by their ID |
| get_user_by_emailB | Get a user by their email |
| get_user_by_nameC | Get a user by their last name |
| get_user_by_first_nameC | Get a user by their first name |
| get_all_user_assetsC | Get all the assets for a user |
| get_user_assets_by_typeD | Get user assets by type |
| update_user_detailsC | Update details of an existing user by their ID |
| transfer_all_assetsC | Transfer all assets from one user to another |
| deactivate_userC | Deactivate a user account |
| reset_user_passwordC | Reset a user's password by their ID |
| get_all_job_messagesC | Get all the messages for a job |
| get_job_by_idC | Retrieve details about an existing job and its current state |
| get_job_output_dataC | Get the output data generated by a job. This will return a list of file paths to the output data. The output data is stored in the temp directory of the server. |
| get_all_schedulesB | Get the list of all schedules of the Alteryx server |
| get_schedule_by_idC | Get a schedule by its ID |
| deactivate_scheduleC | Deactivate a schedule by its ID |
| activate_scheduleB | Activate a schedule by its ID |
| update_schedule_name_or_commentC | Update a schedule name or comment by its ID |
| change_schedule_ownerC | Change the owner of a schedule by its ID |
| get_all_credentialsB | Get the list of all accessible credentials of the Alteryx server |
| get_credential_by_idC | Get the details of an existing credential |
| lookup_connectionC | Lookup a DCM Connection as referenced in workflows |
| get_connection_by_idC | Get a connection by its ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jupiterbak/AYX-MCP-Wrapper'
If you have feedback or need assistance with the MCP directory API, please join our Discord server