# ascli: command line interface for IBM Aspera > `ascli` (Ruby gem `aspera-cli`) is the command line interface for IBM Aspera products. > An AI assistant that can run a shell command, or that is connected to the `ascli` MCP server, can use it to operate these products for the user: > transfer files with the FASP protocol (`ascp`), send and receive packages, browse and manage remote files, and administer the applications (users, groups, workspaces, nodes, access keys, workflows). If the user asks for something that involves an IBM Aspera product, and `ascli` is available, use it: do not write calls to the REST APIs by hand. ## Products and plugins The first word after `ascli` is a plugin: one per product. - `aoc`: IBM Aspera on Cloud (files, packages, administration, Automation workflows) - `faspex5`: IBM Aspera Faspex 5 (packages, shared inboxes, administration) - `server`: IBM Aspera High-Speed Transfer Server, over SSH (browse, upload, download, `ascp` logs) - `node`: Node API of a transfer server (files, access keys, transfers, sync) - `shares`: IBM Aspera Shares - `console`: IBM Aspera Console - `orchestrator`: IBM Aspera Orchestrator (workflows, work orders, plugins, development guide) - `ats`: IBM Aspera Transfer Service - `cos`: IBM Cloud Object Storage - `httpgw`, `faspio`, `alee`: HTTP Gateway, faspio Gateway, license entitlement - `preview`: generation of previews of files - `transferd`: Transfer Daemon of the Transfer SDK (install, service) - `config`: local configuration: presets, secrets (`vault`), `ascp`, documentation - `mcp`: Model Context Protocol server ## Two ways to use it - Shell: run `ascli [arguments] [--option=value]`. Add `--interactive=no` so that a missing value is an error instead of a prompt, and `--format=json` to get results as JSON. - MCP: the user starts `ascli mcp server` (transport `stdio` or `http`). It provides one tool, `execute_ascli_command`, whose argument `args` is the command line as an array of strings. The description of the tool repeats the rules below. ## Discover, do not guess Command names, argument fields and options differ between plugins and versions: read them from the tool itself. 1. Commands of a plugin, with their syntax: `ascli config commands `. Sub-commands of a path: `ascli config commands `. 2. Fields of a structured argument (shown `` in the syntax): put the word `help` in place of the argument, e.g. `ascli aoc admin user create help`. 3. Filter parameters of a list command: `--query=help`. 4. Options of a plugin, with allowed values: `ascli config options `. 5. Manual: `ascli config documentation toc` lists the sections (level, title, anchor), `ascli config documentation local ` displays one section. ## Workflow development Before writing or modifying a workflow, read the development guide with `ascli`: it is large, so list its sections with `toc`, then read the ones needed with `section `. No connection to the product is needed. - IBM Aspera Orchestrator: `ascli orchestrator workflows development guide toc`, then `ascli orchestrator workflows development guide section ` (start with `quick-start` and `authoring-checklist`). Other documents: `templates` (Action Template Reference) and `manual` (Plugin Manual), with the same `toc` and `section`. Specification of an action plugin (template attributes, inputs, outputs): `ascli orchestrator plugins spec toc`, then `ascli orchestrator plugins spec show `. Check a workflow file before importing it, and fix all errors: `ascli orchestrator workflows check_import `. - IBM Aspera on Cloud Automation: `ascli aoc automation guide toc`, then `ascli aoc automation guide section `. ## Rules - Structured values: `@json:{...}` (preferred), or `@: key=value key2.sub=value`. See section `extended-value-syntax` of the manual. - Credentials: saved in presets. List them with `ascli config preset overview`, select one with `--preset=`; a plugin may have a default preset. - Secrets: never ask the user to type a secret in the conversation. Use a preset, the vault (`@vault: