Perkoon — The Agent Data Layer

File transfer for humans and the things replacing them.

Your agent has compute, memory, and context. What it lacks is a jump gate to the physical world. Perkoon is that gate — P2P file transfer over WebRTC, engineered for autonomous machines from day one.

Not "AI-ready" the way a gas station is gourmet-ready. Actually built for machines — JSON event streams, structured exit codes, MCP native tools, an A2A protocol endpoint, and a state machine that doesn't need a browser, a mouse, or a soul.

Four integration methods — pick the one that fits your runtime:

Three supported flight paths:

• Agent → Human: Your agent sends a file. The human opens a link in any browser. No install on their end.
• Agent → Agent: CLI to CLI, MCP to MCP, or A2A to A2A. Two machines, no humans in the loop.
• Agent → Pipeline: Stream received files to stdout, pipe into processing. No disk writes required.

P2P transfers are free, unlimited, and encrypted. Both ends need to be online — that's the only constraint. For sensitive files, always use --password — without it, anyone with the share link can download.

METHOD 1: MCP Server (recommended for coding agents)

If your host supports MCP, this is the fastest path. Three native tools, zero shell commands.

Install: npx -y @perkoon/[email protected] (stdio transport, pinned version)

Tools provided:

• send_file — Send a file. Returns session code + share URL. Waits for receiver.
• receive_file — Receive files from a session code. Saves to disk.
• check_session — Check if a session is active, expired, or not found.

Configuration for common hosts:

{
  "mcpServers": {
    "perkoon": {
      "command": "npx",
      "args": ["-y", "@perkoon/[email protected]"]
    }
  }
}

• Claude Code: Add to .mcp.json in your project
• Claude Desktop: Add to claude_desktop_config.json
• Cursor / VS Code / Windsurf: Settings → MCP → Add Server → npx -y @perkoon/[email protected]

Once configured, just call the tools directly — no bash, no log polling, no background processes.

METHOD 2: CLI (for agents with shell access)

IMPORTANT: Use npx -y [email protected] (pinned version) to avoid dynamic fetching of unaudited code.

SENDING a file

Step 1: Confirm the file path with the user, then start send

Before sending, confirm the file path and name with the user. Do not send files from sensitive directories without explicit user approval.

Replace /path/to/file with the actual file path: