Documentation

Connect Ferry to anything

Step-by-step guides for every kind of connection Ferry supports — and how to hand it all to Claude. Pick your storage below.

Adding a connection

Every connection type follows the same four steps — only the fields change.

  1. 1

    Open the connection form

    Click New connection in the sidebar (or Manage… → New). Give it a name, and optionally a folder to keep things tidy.

  2. 2

    Pick the protocol

    Choose the type that matches your server or storage from the Protocol dropdown. Ferry then shows exactly the fields that type needs.

  3. 3

    Fill in the details

    Enter the fields shown below for your connection type. Passwords and keys are encrypted at rest — nothing is stored in plain text.

  4. 4

    Test, then save

    Click Test to confirm it connects, then Save. Your connection appears in the sidebar — and becomes available to the CLI and to Claude.

Connection guide

SFTP server

Secure file transfer over SSH — the usual way to reach a Linux server, VPS, or managed host.

Where to get the details: Your host or server administrator provides the hostname, username, and a password or SSH key. On the first connect, Ferry shows the server’s host-key fingerprint and asks you to trust it — accept only if it matches what your host published.

New connection
ProtocolSFTP server ▾
Hostsftp.example.com
Port22
Usernamedeploy
Password•••••••• — or use a key
Private key file~/.ssh/id_ed25519 (optional)
Start folder/var/www (optional)

The connection form, filled in for SFTP server.

Connection guide

FTP / FTPS server

Classic FTP, with TLS encryption (FTPS) on by default. Common on shared web hosting.

Where to get the details: Find these in your web host’s control panel (cPanel, Plesk…) under FTP accounts. Keep FTPS on unless your host doesn’t support it — plain FTP sends your password unencrypted and is often blocked on VPNs.

New connection
ProtocolFTP / FTPS server ▾
Hostftp.example.com
Port21
Usernameuser@example.com
Password••••••••
Use FTPS (TLS)On (recommended)
Start folderpublic_html (optional)

The connection form, filled in for FTP / FTPS server.

Connection guide

Amazon S3

Amazon Web Services’ object storage.

Where to get the details: Create an access key for an IAM user that can reach the bucket (AWS console → IAM → Users → Security credentials). Grant only the S3 permissions you need.

New connection
ProtocolAmazon S3 ▾
Bucketmy-app-assets
Regionus-east-1
Access key IDAKIA…
Secret access key••••••••
Start prefixuploads/ (optional)

The connection form, filled in for Amazon S3.

Connection guide

Google Cloud Storage (service account)

Google’s object storage using a service-account key — the native Google way.

Where to get the details: In the Google Cloud console, create a service account with access to the bucket, add a JSON key (IAM & Admin → Service Accounts → Keys), and paste the whole JSON file’s contents into the field.

New connection
ProtocolGoogle Cloud Storage (service account) ▾
Bucketmy-gcs-bucket
Service-account JSON{ "type": "service_account", … }
Start prefixexports/ (optional)

The connection form, filled in for Google Cloud Storage (service account).

Connection guide

Google Cloud Storage (HMAC keys)

Google Cloud Storage through its S3-compatible API, using HMAC keys. Handy if you already work with S3 tools — it behaves just like Amazon S3 with a preset endpoint.

Where to get the details: In the Google Cloud console open Cloud Storage → Settings → Interoperability and create an HMAC key (for your account or a service account). The endpoint is filled in for you — https://storage.googleapis.com — so you only need the bucket and the two keys.

New connection
ProtocolGoogle Cloud Storage (HMAC keys) ▾
Bucketmy-gcs-bucket
HMAC access keyGOOG1E…
HMAC secret••••••••
Endpoint URLhttps://storage.googleapis.com
Regionauto
Start prefix(optional)

The connection form, filled in for Google Cloud Storage (HMAC keys).

Connection guide

S3-compatible storage

Any storage that speaks the S3 API — MinIO, Backblaze B2, Wasabi, DigitalOcean Spaces, and more.

Where to get the details: Get the endpoint URL, region, and keys from your provider’s console. Ferry uses path-style addressing, which every S3-compatible provider supports.

New connection
ProtocolS3-compatible (MinIO, B2, Wasabi…) ▾
Endpoint URLhttps://s3.us-west-002.backblazeb2.com
Bucketmy-bucket
Regionus-west-002
Access key
Secret key••••••••
Start prefix(optional)

The connection form, filled in for S3-compatible storage.

Your credentials

Kept safe, and portable

Every password and key you enter is encrypted at rest with AES-256-GCM in a single connections.json file on your machine — never plain text. That file is portable, so you can back it up or move it to another computer. Ferry also verifies SSH host keys and TLS certificates, prompting before it trusts anything new.

For Claude

Using Ferry with Claude

Install the ferry command and the Ferry skill, and Claude can move files across these connections in plain language — without ever seeing a password.

  1. 1

    Install the command

    In Ferry, open Command-Line Tool and click install (details on the CLI page).

  2. 2

    Install the skill

    Open Claude Skills and click install — or download SKILL.md from the Claude page.

  3. 3

    Just ask

    “Upload this to my web server,” “grab last night’s backups.” Claude picks the right connection by name and runs Ferry.

Ready to connect?

Download Ferry, add your first connection, and start moving files.