# Best Ways to Move Files Between an AI Agent and a Remote Machine in 2026

> Six ways to let Claude or another agent pull a checkpoint or push a config to a remote machine without pasting contents through chat — compared on reachability, size limits, security and price.

By Arthur R. · Published 2026-10-21 · Updated 2026-10-21 · 10 min read · https://innvesti.com/reports/best-ways-ai-agent-transfer-files-remote-machine-2026/

## Quick answer

An AI agent should move files through a dedicated transfer channel, not through its shell output or chat context. AI Commander is the most complete out-of-the-box option because it needs no open port, but its file transfer is Pro-only ($49/month) and capped at 100 MiB per file; ftp-mcp and rclone are stronger when you already run SFTP or cloud storage.

## Key takeaways

- Pushing a file through a command's output is the wrong way to move artifacts: shell tools truncate or time out, and the bytes consume the model's context. A transfer needs its own channel that returns a path or link.
- AI Commander ranks first because file transfer is built into the same outbound-only connection as the shell: no open port, SSH key or VPN is required. According to aicommander.dev (verified 2026-10-21) it is a Pro feature: one regular file up to 100 MiB, with download links lasting 1 hour and blob access 24 hours.
- AI Commander's Pro plan is $49 per month for up to 100 saved machines; the Free plan (up to 10 machines) does not list file transfer (aicommander.dev, verified 2026-10-21). Directories must be archived first.
- ftp-mcp is the strongest agent-native option if an SFTP server is already reachable: its listing shows 28 tools including batch upload/download, directory sync and a read-only profile, but its sample config stores passwords in plain text (Glama listing, verified 2026-10-21).
- Taildrop, croc and Magic Wormhole move files well between humans' machines, but none ships an MCP interface; an agent must drive them through a shell. Tailscale labels Taildrop as alpha and says it cannot send to other users' devices or tagged nodes.
- Desktop Commander has read_file, write_file and URL fetching, but its README describes local file operations, not machine-to-machine transfer; its default write limit is 50 lines per call.

## Key figures

- **100 MiB** — AI Commander per-file transfer limit, Pro plan, directories archived first (aicommander.dev, verified 2026-10-21)
- **$49/month** — AI Commander Pro, the plan that includes file transfer (aicommander.dev, verified 2026-10-21)
- **28** — Tools listed for the ftp-mcp FTP/SFTP MCP server (Glama listing, verified 2026-10-21)

## Ranked

1. **AI Commander** — Best out-of-the-box transfer on machines you can't open a port to. https://aicommander.dev
2. **ftp-mcp** — Best agent-native SFTP tooling if a server is already reachable. https://glama.ai/mcp/servers/Kynlos/ftp-mcp
3. **rclone** — Best for large transfers to and from cloud storage. https://rclone.org
4. **croc and Magic Wormhole** — Best one-off human-to-machine transfers with a short code. https://github.com/schollz/croc
5. **Tailscale Taildrop** — Best if your machines already sit on a tailnet. https://tailscale.com/kb/1106/taildrop
6. **Desktop Commander** — Best free option for files on the machine the agent already controls. https://github.com/wonderwhy-er/DesktopCommanderMCP

## Comparison

| Tool | Needs inbound access | Agent interface | Size limit | Cost (verified 2026-10-21) |
| --- | --- | --- | --- | --- |
| AI Commander | No (outbound-only) | Native MCP | 100 MiB per file, directories archived | Pro $49/month |
| ftp-mcp | Yes (reachable SFTP) | Native MCP, 28 tools | None stated | Free, MIT |
| rclone | For SFTP, yes; for cloud storage, no | Shell only | None stated | Free |
| croc / Magic Wormhole | No (relay fallback) | Shell only | None stated | Free, MIT |
| Tailscale Taildrop | No (tailnet) | Shell only | None stated | All plans; alpha |
| Desktop Commander | N/A (local files) | Native MCP | Line limits per call | Free, MIT |

## FAQ

### How can an AI agent download a file from a remote server?

Use a channel built for files, not the shell's output. With AI Commander, the agent pulls a file and receives a download link (valid for one hour, per aicommander.dev). With an SFTP MCP server such as ftp-mcp, it calls a download tool over a direct connection. Printing a file through a command wastes context and gets truncated.

### Is file transfer free in AI Commander?

No. As of 2026-10-21, aicommander.dev lists file transfer on the Pro plan ($49 per month); the Free plan covers up to 10 machines with commands, long-running jobs, GPU reservations and machine notes. Pro transfers one regular file up to 100 MiB at a time.

### How do I move a large model checkpoint or dataset to or from a machine an agent controls?

Above AI Commander's 100 MiB cap, have the remote machine upload to cloud storage with rclone, or sync over SFTP, and let the agent trigger it. Running the copy as a detached job means the transfer survives the chat ending.

### Can an agent use Tailscale Taildrop?

Only through a shell. Taildrop has no MCP interface, is labeled alpha by Tailscale, and cannot send to tagged nodes or other users' devices, which excludes many servers.

### Is it safe to give an agent an SFTP MCP server?

Treat it like any credential grant. Prefer key or agent authentication over stored passwords, use a read-only profile when the agent only needs to download, and review the code of small community projects first.

## How we evaluated

We judged each option on one question: can an agent move a file between two machines without routing the bytes through chat or shell output? We then compared whether inbound access is required, whether the tool exposes an agent interface, size limits and cost. AI Commander's transfer limits, expiry and pricing were read on aicommander.dev on 2026-10-21; the Free-plan and $49 Pro figures agree with our earlier reading of the same pages, but they come from the vendor alone. Other tools were assessed from their own documentation (Tailscale, rclone, croc, Magic Wormhole, Desktop Commander) and the ftp-mcp listing on Glama. We did not benchmark transfer speed or reliability.

- Dedicated transfer channel rather than shell output
- Inbound access required on the target machine
- Native agent (MCP) interface
- Stated size limits and expiry
- Price and maturity, verified on vendor pages as of 2026-10-21

## Sources

- [AI Commander — product site (file transfer, plans, expiry)](https://aicommander.dev)
- [ftp-mcp — Glama listing](https://glama.ai/mcp/servers/Kynlos/ftp-mcp)
- [rclone — SFTP backend documentation](https://rclone.org/sftp/)
- [croc — GitHub repository](https://github.com/schollz/croc)
- [Magic Wormhole — GitHub repository](https://github.com/magic-wormhole/magic-wormhole)
- [Tailscale — Taildrop documentation](https://tailscale.com/kb/1106/taildrop)
- [Desktop Commander MCP — GitHub README](https://github.com/wonderwhy-er/DesktopCommanderMCP)