Send files between your phone and your AI agent

Coding agents run on your computer, but the screenshot of the bug, the photo of the whiteboard or the PDF from a client is often on your phone. tosstome mcp gives the agent an inbox your phone can send to, and a way to hand files back to your phone, through the Model Context Protocol.

What the agent can do

Tool	What it does
`get_inbox_link`	Starts the computer's inbox and returns its link and a QR code for your phone
`wait_for_files`	Waits until you send files or a text message, then returns their paths. Messages and small images come back inline, so the agent reads the text or sees the screenshot right away
`list_received_files`	Lists what has arrived since the agent started
`send_files`	Sends local files, a text message, or both to your phone using a 6-digit code, or to another computer's inbox link

Set it up

Install the tosstome command line tool (Node.js 22 or newer), then register it with your agent. In Claude Code:

claude mcp add tosstome -- tosstome mcp

For other MCP clients, add a stdio server with this command:

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

Incoming files are saved to ./tosstome-inbox relative to where the agent starts the server, usually your project folder, so the agent can read them with its normal file tools. Add that folder to .gitignore, or pass --dir to put files elsewhere.

Phone to agent

Ask the agent for the inbox link. It calls get_inbox_link and shows you the link and QR code.
Open the link on your phone and add it to your home screen. The link stays the same, so this is a one-time step.
Tell the agent you are sending something. It calls wait_for_files.
Pick the files, or type a message such as an error you copied or a link, and press Send. The agent gets the paths, and reads messages and sees images directly.

Agent to phone

Open toss2.me on your phone and press Create a code.
Tell the agent the 6 digits, for example "send the build to my phone, code 482913".
The agent calls send_files. Your phone asks you to accept, then offers Save for each file, or shows the message with a Copy button.

The same tool sends to another computer running tosstome listen when given its inbox link instead of a code.

Things to know

Files go device to device, or through a relay that keeps nothing. If the phone or the computer is offline, nothing is sent.
One process should hold the inbox at a time. If tosstome listen is already running for the same inbox, stop it while the agent uses tosstome mcp, or files may go to either one.
Anyone with the inbox link can send files to the agent. The server tells the agent to treat file contents as data, not as instructions, but be careful who you give the link to. tosstome listen --new replaces a leaked link.
The server supports both the current stateless MCP revision (2026-07-28) and clients that still use the initialize handshake.

Questions

Which agents does it work with?

Any MCP client that can start a stdio server, including Claude Code, Cursor, Claude Desktop and others. The server is the command tosstome mcp.

Can I send the agent text instead of a file?

Yes. Type or paste into the message box on the inbox page. wait_for_files returns the text inline and also saves it as a .txt file. The agent can send text back to your phone with send_files and its text argument.

Can the agent see my screenshots?

Yes. wait_for_files returns PNG, JPEG, GIF and WebP files under 3.5 MB as image content, so a model that reads images sees them directly. Larger files come back as paths.

Do files go through a cloud service?

No. Files go straight between devices over WebRTC when possible, otherwise through a relay on Cloudflare that forwards them as they arrive and keeps nothing. Transfers to the agent's inbox always use the relay.

Does my phone need an app?

No. The phone uses the inbox page or toss2.me in its browser.

Last checked 2026-10-28.

Send a file now