Enables AI agents to securely send and receive files, text, and media between a terminal and paired devices via end-to-end encryption.
Also known as paironce/cli, cli
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.11.4
- Last commit
- Nov 7, 2026
- License
- Apache-2.0
What is PairOnce MCP?
PairOnce enables AI agents to securely send and receive files, text, and media between a terminal and paired devices via end-to-end encryption.
Summary generated from the project's README
About PairOnce MCP server
PairOnce provides a secure way for AI agents to exchange files, text, and media with your personal devices. By running the server via the npx paironce mcp command, an agent can interact with any device running a web browser, such as an iPhone, Android, or desktop computer. This setup requires no account and uses end-to-end encryption to protect your data. The connection is established through a six-digit pairing code that you approve on your mobile or desktop device.
Developers can use this server to bridge the gap between a terminal environment and the physical world. The agent can send build logs to your phone or request specific items like a photo of a hardware label or a document scan. It includes specialized tools for visual assistance, allowing the agent to request camera or screen frames to guide you through manual tasks. The server maintains a connection for 30 minutes after the last tool call to ensure smooth workflows without constant manual re-approval.
What you can do with it
- 1Transfer terminal data to mobileYou can instruct an AI agent to send a specific build log or file directly to your smartphone.
- 2Capture physical world informationAn agent can ask you to take a photo of a specific object to help it complete a task.
- 3Receive scanned documents into a workspaceYou can have an agent wait for you to upload scans or photos from your phone into a local folder.
- 4Visual step-by-step guidanceThe agent can request periodic still images from your camera or screen to assist with complex procedures.
Written from the project's README. Every use case is checked against a quote from it.
How to install PairOnce MCP
Formats verified 10 Nov 2026Install PairOnce MCP in Claude Code
$ claude mcp add cli -- npx -y paironceInstall PairOnce MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"paironce"
]
}
}
}Install PairOnce MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"paironce"
]
}
}
}Install PairOnce MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"paironce"
]
}
}
}Install PairOnce MCP in Codex
~/.codex/config.toml
[mcp_servers.cli] command = "npx" args = ["-y", "paironce"]
Install PairOnce MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"paironce"
]
}
}
}Configuration
PAIRONCE_NAME
| Name | Description | |
|---|---|---|
| PAIRONCE_NAME | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablepaironce/cli is public and reachablegithub.com/paironce/cli ↗Pass
- Package names this repository as its sourcepaironce names paironce/cli as sourcenpmjs.com/package/paironce ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for paironcenpmjs.com/package/paironce/v/0.11.4#provenance ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/paironce/cli ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from paironcePass
- No critical advisory in the package or its dependencies21 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubpaironce
Send files and text from a terminal to your own phone or computer with PairOnce. Pair once with
a six-digit code; after that, npx paironce send report.pdf puts the file on your phone. End-to-end encrypted, direct
between the devices whenever the network allows, and through an encrypted relay when it does not. No account.
npx paironce pair # shows a code: type it at paironce.com on your phone
npx paironce send build.zip # sends to the paired device
npx paironce text "https://example.com/some/long/link"
npx paironce receive --to ./inbox # receives files sent from the phone
The other device is any browser with https://paironce.com open: iPhone, Android, Windows, Mac or Linux. Nothing to install there.
Commands
| Command | What it does |
|---|---|
paironce pair |
Shows a six-digit code. On the other device, open paironce.com, choose Enter a code and type it. Both screens show the same safety code; approve the device in the terminal. |
paironce pair 123456 |
Joins with the code the other device shows, for a person at this terminal. |
paironce send <file>... |
Sends files to the paired device. With several paired devices, add --to "<name>". The other device accepts each file before it arrives. |
paironce text "<message>" |
Sends a message or a link. |
paironce receive |
Receives files into the current folder (--to <folder>). Asks before each file; --yes accepts every file during this run. Large files are written straight to disk, so they can be as large as the sender may send, and one cut off continues when it is sent again. |
paironce devices |
Lists paired devices. |
paironce forget <name> |
Forgets a paired device. |
paironce mcp |
Runs as an MCP server for AI agents. |
--name "<name>" (or the PAIRONCE_NAME variable) sets what the other device shows for this one, for example
--name "Build server". The key stays the same, so paired devices still know it. --agent marks this device as an AI
agent on the other device (the MCP server always does). The MCP server stays connected for 30 minutes after its last tool call, so the next task needs no tap on your device; you see it as connected and can end it there. The MCP tools save inside the folder the server runs in (inbox by default). --ephemeral uses a throwaway identity in a temporary folder,
which the other device forgets after a day without a connection: right for a sandbox that is thrown away.
When a paired device is not connected, the command asks it to connect: PairOnce on that device shows "Windows · Terminal wants to reconnect" with a Connect button.
Use it from an AI agent (MCP)
paironce mcp gives an agent ten tools:
| Tool | What it does |
|---|---|
pair_device |
Pairs one of your devices. The agent gives you a six-digit code; you open paironce.com on that device, choose Enter a code and type it. The agent then tells you a safety code, and goes on only after you say your device shows the same. Once per device. |
send_file, send_text |
Sends to a paired device; you accept every file there. |
receive_files |
Waits while you send files from your device (a photo of a whiteboard, a scan, a document) and saves them into ./inbox. |
request_photo, request_scan, request_file |
Asks for something specific, with the reason. Your device shows the request; you take the photo, scan the pages or choose the file there, or decline. Saved into ./inbox. |
watch_frames, watch_stop |
Asks to see your camera or screen, with the reason. You share it on your device, or decline; the agent then gets a still picture each time it asks (at most two a second) and can guide you step by step. Your device shows the share and a stop button; it ends when either side stops it. |
list_devices |
Lists the paired devices. |
The agent reaches only devices you paired and approved, and nothing arrives anywhere unasked. Your device marks it Agent when it asks to be approved and in your saved devices. Design and plans: Agent as a Device.
send_file does not send hidden files and folders (such as .env or .ssh), Windows's AppData, a Mac's Library or this
device's own PairOnce files; you can still send those yourself with paironce send. A file that arrives after receive_files
or a request stopped waiting is saved in the folder it was accepted for, and the next receive_files reports it. Changes in
each version are in the releases.
Claude Code:
claude mcp add paironce -e PAIRONCE_NAME="Claude Code · Agent" -- npx -y paironce mcp
# in a throwaway sandbox: ... -- npx -y paironce mcp --ephemeral
# on Windows, through cmd: claude mcp add paironce -- cmd /c npx -y paironce mcp
Other clients (Cursor, Claude Desktop and others), in their MCP configuration:
{ "mcpServers": { "paironce": { "command": "npx", "args": ["-y", "paironce", "mcp"], "env": { "PAIRONCE_NAME": "Cursor · Agent" } } } }
Then ask: "pair with my phone", "send the build log to my phone", or let the agent ask you: "I need a photo of the label on the back of the router".
How it works
The CLI runs the same connection code as paironce.com: the PairOnce protocol and @paironce/core for pairing and encryption, with WebRTC from node-datachannel for direct connections and @roamhq/wrtc (libwebrtc) for the relay. Files and messages are encrypted on this computer and decrypted on the other device; the PairOnce service only introduces the two devices and, when needed, relays encrypted bytes it cannot read.
This computer's device key and the list of paired devices are kept in ~/.paironce (or $PAIRONCE_HOME), readable only
by you. The private key never leaves this computer.
It connects directly whenever the networks allow it, otherwise through the encrypted relay over UDP, TCP or TLS on port
443, and where even that is blocked, through the PairOnce tunnel: the same encrypted data over a secure WebSocket to
paironce.com. So it works on servers, in containers that block UDP, and behind a web proxy (HTTPS_PROXY is used
automatically). In a cloud sandbox with an allow-list, such as Claude Code on the web, add paironce.com to the allowed
domains. PAIRONCE_DEBUG=1 shows each step of connecting.
Requires Node.js 22 or later on Windows, macOS (x64 and arm64) or Linux (x64 and arm64).
License
Apache-2.0. PairOnce is a trademark of its owner; see https://paironce.com.
PairOnce MCP questions
How do I add PairOnce MCP to Claude Code?
Run claude mcp add cli -- npx -y paironce in your terminal. Add --scope user to make it available in every project.
How do I add PairOnce MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I pair my device with an AI agent?
The agent provides a six-digit code which you enter at paironce.com on your device, then you approve the safety code shown on both screens.
Is my data private during transfer?
Yes, all files and messages are end-to-end encrypted, and the private key never leaves your computer.
Does the agent need to stay connected constantly?
The MCP server remains connected for 30 minutes after its last tool call to allow for subsequent tasks without re-pairing.