MCP connector

Yogfile is a drive first. The hosted MCP connector lets an agent use that same durable namespace instead of a separate chat attachment store. It can organize files, keep state between runs, hand work to another model, and create a link only when a person needs access.

Connect a client

The hosted server is available at:

https://mcp.yogfile.com/mcp

There is no vendor-specific API key. OAuth connects a Yogfile account, with optional MFA, to any compatible MCP client.

claude mcp add --transport http yogfile https://mcp.yogfile.com/mcp

Connect an account

A Yogfile account is a random 16-digit credential, with no email, password, or third-party login. The authorization page can create one and lets you copy it without rendering the complete number on screen. Store it in a password manager. Reconnecting with the same number gives the agent the same drives back.

MFA is off by default. Anyone with the complete account number can connect until you enable it in Yogfile settings. With MFA on, the page asks for a TOTP authenticator code or one recovery code.

Authorization uses OAuth 2.0 with PKCE. The encrypted refresh token contains a revocable device authorization, never the account number. Access tokens last a day and renew automatically.

Available tools

upload_file

Writes text, base64 content, or a public URL into a drive path. The hosted connector accepts files up to 100 MB. The local binary accepts a disk path and streams larger files directly to storage.

share_link

Mints a short-lived signed capability when a machine needs raw bytes. The file remains in the drive. Only the capability expires, after ten minutes by default.

list_files

Lists drives, folders, and files with stable IDs, sizes, and lifecycle dates where one was explicitly set.

create_folder

Creates a nested path such as reports/2026/q3. Missing levels are created in one operation.

create_drive

Creates a persistent namespace with a short ID, real folders, optional passphrase protection, and an optional default lifecycle policy.

delete_file

Moves a file to Yogfile Trash. Its stable page stops working and no new download capability can be issued. The owner can restore it for 30 days before permanent deletion.

Hosted connector limits

• Files persist until they are deleted or an explicit lifecycle policy expires them.
• A single hosted connector upload is capped at 100 MB.
• The local binary streams large files from disk without that connector-body limit.
• Transfer speed is unlimited during launch.
• Public links retain a two-connection concurrency cap.
• Signed download capabilities last ten minutes by default.

Local MCP binary

The local binary is useful when an agent needs to upload files already on disk. Install the latest release with:

curl -sSfL https://www.yogfile.com/install.sh | sh

The connector is open source at github.com/sifrah/yogfile-mcp. Custom runtimes that do not speak MCP can use the same drive through the HTTP API.