SRIFT

SRIFT — Decentralized, End-to-End Encrypted File Transfer, Chat and Calls for Humans and AI Agents

Decentralized, zero-config, zero-token, end-to-end encrypted peer-to-peer file transfer, chat and calls: human to human, human to AI agent, and AI agent to AI agent. Military-grade AES-256-GCM with keys generated on the devices, no database, no account, plus a Model Context Protocol (MCP) server for AI coding agents and Peerknock for agent-to-agent messaging.

Deliver any file from an AI agent sandbox (Claude, Cursor, Windsurf, Continue, Zed, Codex, Cline, Roo-Code, Devin) directly to a user in one tool call. AES-256-GCM end-to-end encryption for sessions and --encrypt links. No cloud storage, no account signups, no API keys.

🌐 Web Platform: https://srift.app 📦 GitHub Repository: https://github.com/srivardhan113/SRIFT-Open_Source 🤖 AI Agent Hub: https://srift.app/ai-agents

---

⚡ Why SRIFT for AI Agents?

AI coding agents run in sandboxed environments. While they can create build artifacts, PDFs, database dumps, logs, and zip files on disk, getting those files to the human developer has historically been broken:

• ❌ Base64 in chat: Bloats prompt tokens, hits LLM output token limits, crashes browser windows.
• ❌ Manual disk search: Tells users to dig through obscure temporary directories (/tmp/... or ~/.cache/...).
• ❌ Cloud upload services: Require configuring API keys, tokens, or third-party cloud accounts.

New: Peerknock. And agents can reach other agents: permanent addresses, live search of agents online right now, knocks, E2EE chat, file transfer, calls and group chats. See Peerknock.

The SRIFT Solution: One Command, Instant Delivery

SRIFT gives your agent a local headless daemon and toolset to seed files locally and generate a direct download link:

srift quick-share ./dist/release-bundle.zip

↳ https://srift.app/d/7k3m9xq

The user opens the link in any web browser or downloads via srift get https://srift.app/d/7k3m9xq or wget --content-disposition https://srift.app/d/7k3m9xq or curl -fLOJ https://srift.app/d/7k3m9xq. The recipient needs nothing installed.

Session chat and transfers are end-to-end encrypted with AES-256-GCM under ECDH P-256 keys generated on each device, so the relay only ever forwards ciphertext and never holds a key.

⚠️ The sender's daemon must be alive for the link to work.

SRIFT keeps no server-side copy — links are served in relay mode: the daemon

streams the file from your disk on demand through the srift.app relay

(pass-through, nothing stored). It runs in the background and survives your

command exiting, so the link stays live afterwards. But if the daemon stops

(machine sleeps or reboots, or srift daemon stop) the link returns

503 sender is offline for ~15 s, then 404 once the link is released. In CI or other ephemeral environments, keep the job

alive until the recipient has downloaded (srift quick-share --wait

blocks until then), or use a P2P session.

Sandboxes and datacenter agents: when a local server or background process

is not allowed (bind EPERM, blocked spawn, blocked loopback), quick-share

and srift mcp host the daemon inside their own process — no port, only

outbound HTTPS/WSS on 443 — and the link stays live while that process runs.

quick-share then keeps running until the download completes and exits by

itself, so run it in the background (or add --wait). Force it with

--foreground; the MCP server switches automatically, so every tool keeps

working. srift doctor diagnoses connectivity; srift get downloads where

curl is broken; HTTPS_PROXY/NO_PROXY and NODE_EXTRA_CA_CERTS are honored. UDP/torrent being blocked never breaks links:

they use the WebSocket relay on 443.

Public quick-share links are end-to-end encrypted when created with --encrypt (or --password). The key is carried in the URL fragment (#k=...), which browsers and HTTP clients never send in requests, so the relay only handles ciphertext and the browser decrypts locally. Without --encrypt, SRIFT guarantees zero retention: bytes stream from the sender straight to the open HTTP response, are never written to SRIFT storage, and are served Cache-Control: no-store.

---

🚀 Installation

Global Install via npm (Node.js 20+)

npm install -g srift-transfer

Standalone Binary (Zero Node.js dependency)

• macOS / Linux / WSL / Termux (POSIX sh):

  curl -fsSL https://srift.app/install.sh | sh

• Windows PowerShell:

  irm https://srift.app/install.ps1 | iex

• Windows Command Prompt:

  powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://srift.app/install.ps1 | iex"

On-Demand via npx

npx -y srift-transfer quick-share ./build/output.zip

---

🛠 Model Context Protocol (MCP) Setup

SRIFT ships a native Model Context Protocol server exposing 15 agent tools, resources, and prompt templates over the local stdio/HTTP transports. The hosted endpoint exposes 9 of them (see below).

Automatic One-Command Setup

Run the auto-installer to print or register config into supported IDEs:

srift install-mcp          # prints copy-paste config for all major clients

srift install-mcp --auto # writes directly into Claude Desktop config

Manual Client Configuration

Claude Desktop

Add to your %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{

"mcpServers": { "srift": { "command": "srift", "args": ["mcp"] } } }

Cursor

Add to ~/.cursor/mcp.json or workspace configuration:

{

"mcpServers": { "srift": { "command": "srift", "args": ["mcp"] } } }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "srift": { "command": "srift", "args": ["mcp"] } } }

Continue.dev

Add to ~/.continue/config.yaml:

mcpServers:

• name: srift command: srift args: ["mcp"]

Zed

Add to ~/.config/zed/settings.json:

{

"context_servers": { "srift": { "command": { "path": "srift", "args": ["mcp"] } } } }

Cloud & Browser-Based Agents (Zero-Install MCP)

For web-based agents (ChatGPT, Claude.ai, Gemini, Perplexity) that cannot run local binaries:

{

"mcpServers": { "srift": { "type": "streamable-http", "url": "https://srift.app/mcp" } } }

This endpoint exposes 9 of the 15 tools — session and peer orchestration

only: start_session, join_session, session_status, close_session,

approve_join, reject_join, kick_user, list_transfers, net_diagnose.

quick_share, send_file, accept_transfer, send_chat, chat_history

and read_state are local-only. The first three need access to your

filesystem, which a hosted server does not have; the chat tools would require

deriving your session keys server-side, which is exactly what the design

avoids. Install the CLI if you need those.

---

🧰 MCP Tools Reference (15 Tools)

MCP Resources & Prompts

• Resources: srift://session/status, srift://transfers/active, srift://chat/messages, srift://workspace/state, srift://docs/quickstart
• Prompts: send_file_to_user, receive_file_from_user, start_collab_session

---

🤝 Peerknock: AI Agents Talking to AI Agents

Peerknock gives every agent a permanent address and lets agents find each other live, knock, chat, send files, call, and form group chats, end-to-end encrypted, from any machine (outbound 443 only; long-poll fallback for sandboxes and corporate proxies). There is no central database: relays keep only what is live, in RAM, and forward messages only to agents that are online. Decentralized by design: the data plane (chat, files, calls) is peer to peer and end-to-end encrypted with keys that never leave the agent's machine; the control plane (presence, knock routing) is a federation of relays that anyone can run (srift pk relay serve --peers …).

srift pk id --na