IBM Aspera CLI
OfficialRelated Servers
Alternatives to IBM Aspera CLI
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables SSH command execution, file uploads/downloads, and multi-server management with zero-config inline credentials, supporting async jobs and AI-readable output.32 npm2AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with IBM i (AS/400) systems for RPA automation via 37 tools for 5250 navigation, CL commands, DB2 queries, and system management.MIT
- AlicenseAqualityBmaintenanceLets AI clients execute shell commands and transfer files on remote machines via configured aliases, while keeping credentials and audit logs local.8MIT
- AlicenseNot gradedqualityBmaintenanceAI-powered connection manager with 60+ MCP tools for SSH terminal execution, RDP desktop control, VNC interaction, web session automation, and encrypted credential vault management. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.305 npm20Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to drive IBM i (AS/400) 5250 green-screen sessions — data entry, menu navigation, and automated testing — with a live web viewer where a person can watch or take over. Optionally adds Db2 for i SQL queries, IFS file access, CL commands, compiling, and job log or spooled file reading through the IBM i host servers.14MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely execute shell commands and transfer files on SSH hosts, including jump-host tunneling, background tasks, resumable transfers, and optional approval of destructive commands, while SSH credentials remain in the local process. It runs over stdio or a streamable HTTP daemon and supports auditing, allow/deny lists, and multiple authentication methods.ISC
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its single purpose — run an ascli argv array — is clearly stated and matches its name.
A single tool named execute_ascli_command uses a clean verb_noun convention and is self-describing. With one tool there is no convention mixing to penalize.
A single generic passthrough tool is a defensible design for a large CLI, but it is coarse: agents get no first-class operations and must chain discovery calls before anything. The surface is thin at the tool layer even though the underlying command space is large.
Because it delegates to the full ascli with built-in introspection of commands, options, argument schemas, and docs, virtually every CLI capability is reachable. The gap is ergonomic rather than functional: common workflows (upload, browse, package send) require multi-step discovery instead of dedicated tools.