Transfa
Let your agent upload files and return SHA-256-verified, TTL-signed share links without building a custom file API.
Overview
Transfa MCP is an MCP server for the Build phase that uploads files via Transfa and returns SHA-256-verified, TTL-enforced signed links to your agent.
What is this MCP server?
- Upload any file and receive a signed link with SHA-256 verification and TTL enforcement
- Guest mode without API key (10 MB limit); TRANSFA_API_KEY unlocks full Transfa API at transfa.sh
- Optional TRANSFA_BASE_URL for self-hosted Transfa instances
- npm package transfa-mcp (v1.0.1) with stdio transport
- No account required for basic guest uploads per server description
Community signal: 14 GitHub stars.
What problem does it solve?
Agents and scripts need to share binaries or logs quickly, but rolling custom presigned URL flows steals time from shipping the actual product.
Who is it for?
Solo builders who want zero-account guest uploads for small files or API-key mode for repeatable agent-driven file handoffs.
Skip if: Teams needing enterprise DAM, permanent public hosting, or large-file pipelines without Transfa limits.
What do I get? / Deliverables
Once configured, your agent can upload files and hand back verified signed links without you leaving the coding session.
- Agent-invokable upload tools returning signed Transfa URLs
- Documented env vars for guest vs API-key modes
Recommended MCP Servers
Journey fit
Transfa is registered during build when you connect agents to file handoff, but the same links support ship demos and operate support threads. File upload MCP is agent-tooling integration—ideal subphase for npm-based stdio servers with optional API keys.
How it compares
Ephemeral signed-link MCP, not a cloud storage skill or full S3/IaC module.
Common Questions / FAQ
Who is Transfa MCP for?
Indie developers using MCP agents who need fast, integrity-checked file links for demos, support, or CI artifacts.
When should I use Transfa MCP?
Use it when an agent must upload a file and return a shareable URL during build integrations, pre-release tester handoffs, or ops debugging.
How do I add Transfa MCP to my agent?
Add the transfa-mcp npm stdio server to your MCP config, optionally set TRANSFA_API_KEY and TRANSFA_BASE_URL, then restart your client.