Transfa

What colapsis/transfa MCP server does

The colapsis/transfa MCP server lets an MCP-compatible agent send local files to the hosted transfa.sh service. An upload produces two links: an agent-oriented direct download URL and a browser-friendly sharing page. The response also includes a SHA-256 digest so a receiving process can verify the downloaded file.

The service accepts arbitrary file types. It detects MIME types for more than 100 formats, including machine-learning models, data files, archives, source code, media, and configuration files. Unknown formats are accepted as application/octet-stream.

How it works

The server runs as a Node.js process launched through npx. MCP tool calls are translated into requests to transfa.sh. Uploads can run without credentials in guest mode, with a 10 MB file limit and a maximum 24-hour lifetime. Supplying an API key allows larger files and longer TTLs according to the associated plan.

Each upload has an expiry and can expose download metadata such as size, filename, checksum, download count, active status, and grace-period state. The returned links can be passed to another agent, included in a generated report, or consumed by a script.

Setup and configuration

Start the colapsis/transfa MCP server with:

npx -y transfa-mcp

For Claude Desktop, add the server to the MCP configuration and provide TRANSFA_API_KEY when authenticated uploads are needed:

{
  "mcpServers": {
    "transfa": {
      "command": "npx",
      "args": ["-y", "transfa-mcp"],
      "env": {
        "TRANSFA_API_KEY": "your-api-key"
      }
    }
  }
}

The API key is optional for basic guest uploads. It is required for listing uploads, deleting owned uploads, larger files, and longer retention periods.

Tools and capabilities

The colapsis/transfa MCP server exposes four file-management tools:

• upload reads a path from the local filesystem, sends the file, and returns the agent link, human link, SHA-256 value, and expiry details.
• file_info retrieves upload metadata without downloading the file, including filename, size, checksum, expiry, download count, active state, and grace-period information.
• list_uploads returns recent uploads and requires an API key or credentials saved through the transfa CLI.
• delete_upload removes an upload immediately when the supplied API key matches its owner.

The upload service also supports options such as custom TTLs, password protection, download limits, and filename overrides through its broader API, but the available MCP input surface should be checked before relying on each option.

Limitations and notes

Guest access is restricted to 10 MB files and 24-hour expiry. Authenticated limits depend on the account plan, with documented plan ceilings ranging from 500 MB to 100 GB and TTLs from 48 hours to 180 days. Listing and deletion are not anonymous operations. The server transfers files to the hosted transfa.sh service, so it is not a local-only file exchange mechanism.