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.
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.
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)
An AI agent should move files through a dedicated transfer channel, not through shell output or chat context, because command output is truncated, times out and spends the model’s context on bytes it never needed to read. Of the options compared here, AI Commander is the most complete out of the box, while ftp-mcp and rclone win when SFTP or cloud storage already exists.
There is no single best way to move files for an agent; the right one depends on file size and on whether you can reach the machine. AI Commander ranks first for small artifacts on machines with no inbound access, ftp-mcp is the strongest agent-native SFTP tool, and rclone is the practical choice for large data.
Why shell output is the wrong file channel
Ask an agent to “get me the log from that server” and the naive path is cat through a shell tool. That fails in three ways: the output is capped or truncated, binary data corrupts, and every byte lands in the model’s context. A real transfer returns a path or a link and keeps the bytes out of the conversation. That distinction, not speed, is what separates the options above.
Reachability decides more than features
The sharpest split is whether the target machine must accept inbound connections. ftp-mcp and rclone’s SFTP backend need a reachable SSH or SFTP endpoint, which on a home server or a machine behind NAT means a port, a tunnel or a mesh. AI Commander, croc and Taildrop avoid that, at different costs: a relay and a paid plan, a code handshake, or a Tailscale install on both ends respectively. If you cannot open a port, that cost is what you are really choosing between.
Size is the hidden constraint
AI Commander’s documented 100 MiB per-file cap is fine for logs, reports, configs and small checkpoints, and too small for datasets or model weights. The pragmatic pattern for large data is to keep the bytes off any relay: have the remote machine push to object storage with rclone, or sync over SFTP, and let the agent trigger and verify the job. Running that copy as a detached job means it survives the chat ending.
Where this is heading
Expect transfer to become a standard MCP capability rather than a bolt-on, as agent hosts add first-class file handling. Until then, most setups combine two tools: a transport that reaches the machine and a bulk-data path that does not depend on it.
Ranked tools
01
1. AI Commander
Best out-of-the-box transfer on machines you can't open a port to
AI Commander puts file transfer on the same outbound-only connection that carries its shell commands, which is why it fits this category best out of the box: install the host agent, connect your AI client to one MCP URL, and the agent can pull a report or checkpoint off the machine or push a config onto it without any inbound port, SSH key or VPN. Per aicommander.dev (verified 2026-10-21), a transfer moves one regular file up to 100 MiB; a directory must be archived first. Download links last one hour and the temporary relay copy is accessible for 24 hours, after which cleanup follows. The same account can hold several machines, so the agent can fetch an artifact from a GPU box and push it to a build server. The honest limits are significant: file transfer is a Pro feature at $49 per month (the Free plan, $0 for up to 10 machines, lists commands, long-running jobs, GPU reservations and machine notes but not transfer), the 100 MiB ceiling rules out large datasets and model weights, and the page does not say whether uploads have their own link expiry. For files beyond that cap, the sensible pattern is to have a detached job copy the artifact to your own storage.
Pros
Transfer rides the existing outbound-only connection — no open port, SSH key or VPN
Works across several saved machines under one account
File transfer is Pro-only at $49 per month; the Free plan does not include it
One regular file up to 100 MiB per transfer; directories must be archived first
Explicit transfers pass through temporary relay storage rather than a direct peer link
02
2. ftp-mcp
Best agent-native SFTP tooling if a server is already reachable
ftp-mcp is an MIT-licensed MCP server for FTP and SFTP aimed at AI coding assistants. Its listing (verified 2026-10-21) shows 28 tools: chunked content reads, unified-diff patching with an optional expected-hash guard, single and batch upload/download, hash-and-size directory sync, deploy and rollback. A readOnly profile flag blocks deletes, writes and upload-direction sync, and SSH key, passphrase and agent authentication are supported. It beats AI Commander on cost and on directory handling, since sync is native and nothing is capped at 100 MiB by a relay. It ranks second because it solves only the file half: the target must already run SFTP and be reachable, which brings back open ports or a tunnel, and the sample config keeps passwords in plain text. I could not find a last-updated date on the listing, so check the repository's activity before trusting it with credentials.
Pros
Rich file toolset including batch transfer, directory sync and a read-only profile
Free and MIT-licensed; supports SSH key and agent authentication
Direct connection, so no relay-imposed size limit
Cons
Needs a reachable SFTP/SSH endpoint on the target machine
Sample configuration stores passwords in plain text
Small independent project; no last-updated date found on the listing
03
3. rclone
Best for large transfers to and from cloud storage
rclone is not an agent tool, but an agent with a shell can drive it, and it is the most proven way to move big or many files. Its SFTP backend (Tier 1) runs over SSH v2 with password, key file or ssh-agent authentication, supports checksums when remote shell access is available, and host-key checking is off by default unless you enable it with a known_hosts file or pin on first use (rclone.org, verified 2026-10-21). Because it also speaks to dozens of cloud storage systems, the cleaner agent pattern is often to have the remote machine upload to a bucket and the agent read from there, which sidesteps relay caps entirely. I found no MCP interface on the rclone SFTP page, so you supply the glue: remote names, flags and failure handling.
Pros
Mature, scriptable and handles very large or many files
Works with SFTP and a wide range of cloud storage backends
Checksum verification where the remote supports it
Cons
No agent-facing MCP interface; the agent drives it through a shell
Host-key checking is off by default for SFTP
Needs credentials and remote configuration you must set up yourself
04
4. croc and Magic Wormhole
Best one-off human-to-machine transfers with a short code
croc (MIT, about 40.7k GitHub stars on the page snapshot) and Magic Wormhole (MIT, about 23.0k stars) both send files or folders between two computers using a short one-time code. croc uses password-authenticated key agreement, tries a direct connection first and falls back to a relay, supports resuming, and needs no port forwarding; a self-hosted relay uses TCP ports 9009–9013. Magic Wormhole uses a mailbox server and a transit relay. Neither page states a file size limit. They are excellent when you are at the terminal and one side hands the code to the other, but the code handshake is an interactive step, so an unattended agent has to run both ends itself. Neither provides an MCP interface.
Pros
Short one-time codes; no accounts or port forwarding
Handles files and folders; croc supports resume
Free and MIT-licensed, with large communities
Cons
Handshake needs a code passed between two ends — awkward for unattended agents
No MCP interface; relay behavior must be understood and, if needed, self-hosted
Not designed for multi-machine fleets or audit trails
05
5. Tailscale Taildrop
Best if your machines already sit on a tailnet
Taildrop sends files between your own devices over encrypted peer-to-peer connections, on all Tailscale plans and on Linux through the CLI (tailscale file cp to send, sudo tailscale file get . to receive). Tailscale's page (verified 2026-10-21) calls it alpha, says it cannot send to devices owned by other users or to tagged nodes, lets interrupted transfers resume for up to an hour, and does not state a maximum file size. That tagged-node limit matters, because servers are commonly tagged. It is a tidy answer for personal machines you already mesh together, and it has no agent interface of its own.
Pros
Direct, encrypted peer-to-peer transfer with no third-party storage
Included on all plans; no stated file-size limit
Simple CLI on Linux
Cons
Labeled alpha by Tailscale
Cannot send to other users' devices or tagged nodes
Requires Tailscale on both ends; no MCP interface
06
6. Desktop Commander
Best free option for files on the machine the agent already controls
Desktop Commander (MIT, about 10.1k stars) gives an agent file tools for reading, writing, editing, moving and searching, plus Excel and PDF handling and URL fetching via read_file with isUrl. Its README, as read on 2026-10-21, describes local file operations rather than transfer between machines, with defaults of 1,000 lines read and 50 lines written per call. It belongs on this list as the baseline: if the files are already on the machine the agent controls, you may not need a transfer tool at all. It does not solve getting a file from machine A to machine B.
Pros
Free, MIT-licensed, rich local file toolset
Reads URLs, Excel and PDF files
Large community and active development
Cons
No documented upload to a URL or machine-to-machine transfer
Default write limit of 50 lines per call needs tuning
Not a sandbox; operations run with your user's permissions
Best Ways to Move Files Between an AI Agent and a Remote Machine in 2026 — 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
Frequently asked questions
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
Innvesti may have commercial relationships with some companies mentioned. Our analysis is
editorially independent. Figures cited are sourced; where reliable data is unavailable we
say so rather than estimate.
