
Transfa
io.github.colapsisPublished by GitHub account colapsisv1.0.1Updated Oct 24, 2026
Upload any file, get a signed link. SHA-256 verified, TTL-enforced, no account required.
Overview
Lets an assistant upload local files to a Transfa file-sharing service and get back signed, expiring download links with SHA-256 checksums.
- What you can do
- The server exposes tools to upload a file from the local filesystem and return an agent link, a human share page and a SHA-256 checksum; to fetch metadata for an upload (filename, size, checksum, expiry, download count, provenance fields); to list recent uploads; to delete an upload; and to retrieve all files uploaded under a given run_id as a provenance manifest. Uploads can carry provenance fields such as run_id, step, consumer and intent. Links are TTL-enforced and can be password-protected or limited to a number of downloads.
- When to use it
- Useful when an assistant needs to hand a generated file, report, model or build artifact to a person or another agent without setting up storage. It fits script, CI and agent workflows that move files and need a shareable link plus a checksum.
- Requirements
- Runs locally over stdio, typically launched with npx transfa-mcp, so Node.js is needed. An API key is optional: set TRANSFA_API_KEY for account features such as listing uploads; without it the server works in guest mode with a 10 MB limit. TRANSFA_BASE_URL can point at a self-hosted instance instead of the default service. Network access to the Transfa service is required.
Installation
In SourceWeft
- Open Transfa in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Dead-simple file sharing for developers and AI agents.
Upload with one command. Share with a link. No account required.
[npm version] [npm downloads] [node version] [MIT License] [Hosted service]
Why transfa?
Most file-sharing tools are built for humans clicking through UIs. transfa is built for the terminal — designed to be called from shell scripts, CI pipelines, and AI agents (Claude, GPT, Cursor, etc.) that need to move files without friction.
- No signup required — just install and upload
- Any format, any size — up to 100 GB; ML models, archives, binaries, code, media
- Built for agents — JSON API, SHA-256 checksums, idempotent uploads
- Password protection, download limits, TTL — full control over every link
- 100+ formats detected — MIME type auto-detection including
.gguf,.safetensors,.parquet,.ipynb, and more
Install
Node.js / CLI
Python SDK
MCP server (Claude, Cursor, any MCP-compatible agent)
Or use the raw install script:
Quick start
GitHub Actions
Upload build artifacts, coverage reports, and any CI output straight from your workflow:
All five outputs are available after the step: id, agent-link, human-link, sha256, expires-at.
See colapsis/transfa-action for the full input reference and more examples (password-protected links, self-hosted instances, single-download limits).
API
transfa is fully REST. Every operation the CLI does, you can do with curl or any HTTP client.
Upload
Upload options (form fields or headers):
Download
File info
List uploads
Delete
Supported formats
Over 100 file types with correct MIME detection — including types not in standard MIME databases:
Any other format is accepted as application/octet-stream — nothing is blocked.
Plans
MCP server (Claude, Cursor, and any MCP-compatible agent)
transfa ships an MCP server that lets Claude, Cursor, and any MCP-compatible agent upload and share files autonomously — no shell commands, no infrastructure setup.
Claude Desktop config
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
The API key is optional — the server works in guest mode without one (10 MB / 24h limit).
Available MCP tools
Example agent workflow
When Claude has transfa as an MCP tool, it can:
- Generate a report → call
upload→ get a link → paste the link in the conversation - Pass a file to another agent by sharing the
agent_link - Clean up with
delete_uploadwhen done
Python SDK
See python/README.md for the full API reference.
Use with AI agents (script/subprocess)
transfa is also designed to be called from shell scripts, CI pipelines, and agents that prefer subprocess calls:
Or use the REST API directly — no SDKs, no auth flows, just HTTP.
Self-hosting
Requirements: Node.js 18+, nginx (for SSL/proxy)
See nginx/transfa.conf for a production-ready nginx config.
Environment variables
Security
Found a vulnerability? Please email [email protected] or see SECURITY.md.
Do not open a public issue for security reports.
License
MIT — © 2026 transfa contributors
Source: README.md at commit d665b06
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
