EveryTransfer CLI + MCP server

Send large files from your terminal, or let an AI assistant send them for you. One package, two binaries, one shared API client.

everytransfer send report.pdf
→ https://everytransfer.com/k3n9xq2ab7de/

Install

npm install -g @everytransfer/cli

Or run it without installing:

npx -p @everytransfer/cli everytransfer send report.pdf

Requires Node 20 or newer.

Sign in

Get an API key from https://everytransfer.com/account-api, then:

everytransfer login

The key is stored at ~/.config/everytransfer/config.json with owner-only permissions. For CI or a one-off shell, set an environment variable instead — it takes precedence over the stored file:

export EVERYTRANSFER_API_KEY=your_key

Your plan must include API access. If the key is rejected with "You do not have access to the API", check the API feature on your plan.

CLI

| Command | What it does | | --- | --- | | everytransfer send <files...> | Upload files, print the share link | | everytransfer list | List your transfers | | everytransfer info <id> | Show one transfer and its files | | everytransfer delete <id> | Delete a transfer and its files | | everytransfer projects | List your projects | | everytransfer whoami | Show the signed-in account | | everytransfer login / logout | Manage the stored key | | everytransfer mcp-config | Print the config that connects this to Claude |

et is a shorter alias for the same binary.

Sending

# the basics
everytransfer send report.pdf

# several files in one transfer
everytransfer send *.png

# password, expiry and a download cap
everytransfer send contract.pdf \
  --password hunter2 \
  --expire 7d \
  --limit 3 \
  --name "Signed contract" \
  --message "Countersigned copy, please keep."

--expire accepts 30m, 12h, 7d, 2w, a date like 2026-10-01, or never. The server clamps it to whatever your plan's maximum retention allows, so asking for longer than the plan permits quietly gives you the plan's limit.

Scripting

Every read command takes --json. Exit code is non-zero on failure, so this is safe in a pipeline:

link=$(everytransfer send build.zip --json | jq -r .link)
echo "Build is at $link"

whoami --json redacts the API key, which the underlying endpoint otherwise echoes back.

MCP server

Lets Claude send files for you: "send that log file to my colleague".

Claude Code

claude mcp add everytransfer --env EVERYTRANSFER_API_KEY=your_key -- npx -y -p @everytransfer/cli everytransfer-mcp

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "everytransfer": {
      "command": "npx",
      "args": ["-y", "-p", "@everytransfer/cli", "everytransfer-mcp"],
      "env": { "EVERYTRANSFER_API_KEY": "your_key" }
    }
  }
}

everytransfer mcp-config prints this for you with your key filled in.

Tools

| Tool | Notes | | --- | --- | | send_files | Uploads local files, returns the link. Takes name, message, password, expiry, download limit. | | list_transfers | Read-only. | | get_transfer | Read-only, includes the file list. | | delete_transfer | Marked destructive, and refuses unless confirm is true. | | whoami | Read-only. |

The server talks MCP on stdout and writes all its logging to stderr, so it will not corrupt the protocol stream.

Things worth knowing

Uploads are one request per file. The REST API has no chunked upload, so a file has to fit inside the server's PHP upload limit. Large files that the web uploader handles fine can still be rejected here. When that happens you get a message saying the server rejected it as too large rather than a bare 500.

Folders are not accepted. Zip the folder first, or pass the files inside it.

Rate limit is 60 requests a minute per API key. Files upload one at a time, which keeps a normal batch well inside that. If you do hit the limit the client waits it out rather than failing.

Custom domains. The API never returns which domain a transfer belongs to, so links are always built on the main domain. Everything created through this tool lives there, so its links are correct. A transfer created in the web UI on a custom domain will be shown with a main-domain link, which will not resolve.

Self-hosted / staging

Point it at another installation:

export EVERYTRANSFER_BASE_URL=https://files.example.com

Development

npm install
npm run build      # compile to dist/
npm run typecheck  # no emit

Layout:

src/
  api/client.ts   HTTP client: auth, retries, rate limits, error envelope
  api/types.ts    response shapes
  config.ts       key storage and resolution
  send.ts         create-then-upload, shared by both binaries
  cli.ts          the CLI
  mcp.ts          the MCP server

Both binaries go through send.ts, so the CLI and the assistant behave identically.