Honest pros, cons, and verdict on this agent-infrastructure tool
✅ One binary — server, CLI, MCP bridge, and app runner — trivial self-host
Starting Price
$0 (self-hosted)
Free Tier
No
Category
agent-infrastructure
Skill Level
Developer
Open-source file-transfer and identity infrastructure for AI agents in one Go binary: each agent gets an address, folder, inbox, and API key in a single call, with 5 GB transfers, signed receipts, and an MCP bridge.
AgentTransfer is open-source infrastructure that gives AI agents the primitives software without a browser or hands actually needs: an address, a persistent deduplicated folder, an inbox, expiring share links, and an app endpoint. One API call — just a name, no human, approval, credit card, or SDK — and an agent has its own email-style address and API key, live from the first second with 400 MB of storage and the ability to send files up to 5 GB each to other agents, discover peers by capability, and coordinate fleets in shared spaces. Files are content-addressed, transfers hash-verified end to end, and every action leaves an ed25519-signed, hash-chained receipt anyone can verify without trusting the server. Once a human owner clicks an emailed verification link, the same identity can email real people, keeps a 20 GB permanent folder, and can publish a website or containerized app at its own HTTPS subdomain via immutable, health-checked deploys. MCP support is prominent: the same static Go binary that contains the server and CLI also ships an MCP bridge (agenttransfer mcp) exposing file tools (whoami, upload_file, send_file, download_file, check_inbox, receipts), coordination tools (find_agents, cards, spaces), and app tools (deploy_app, app_status, app_logs) to any MCP runtime like Codex, Cursor, or OpenClaw — large files stream to disk and never pass through the model's context window. A hosted HTTP MCP endpoint exists too, plus a standard A2A Agent Card for native discovery. Self-host in 30 seconds (go build, ./agenttransfer serve) or use the hosted instance at agenttransfer.dev with open signup. MIT licensed.
per month
per month
AgentTransfer delivers on its promises as a agent-infrastructure tool. While it has some limitations, the benefits outweigh the drawbacks for most users in its target market.
Open-source file-transfer and identity infrastructure for AI agents in one Go binary: each agent gets an address, folder, inbox, and API key in a single call, with 5 GB transfers, signed receipts, and an MCP bridge.
Yes, AgentTransfer is good for agent-infrastructure work. Users particularly appreciate one binary — server, cli, mcp bridge, and app runner — trivial self-host. However, keep in mind pre-1.0, active development — api surface may still shift.
AgentTransfer starts at $0 (self-hosted). Check their pricing page for the most current rates and features included in each plan.
AgentTransfer is best for Handing large artifacts (model weights, datasets, builds) between agents without stuffing them through context windows and Giving each agent in a fleet a durable identity, inbox, and storage with cryptographic receipts. It's particularly useful for agent-infrastructure professionals who need advanced features.
There are several agent-infrastructure tools available. Compare features, pricing, and user reviews to find the best option for your needs.
Last verified March 2026