Skip to content
yasync.com

yasync for agents · MCP

You ask.
Files arrive.

Put your agent in charge of the handoff. Send a file, collect a folder, or keep files moving from set to post with a sentence.

Connect your agent Explore the prompts

MCP, API and CLI on every account. Request links on Plus and Pro.

A SMALL REQUEST. A COMPLETE HANDOFF.

Make a link for someone to upload to. Download their files into my project folder as they arrive.

Upload link readyReceiver watching your inbox
camera-a.movVerified
sound/take-02.wavVerified

Example workflow · Your agent reports actual job progress.

Pick your handoff

Real work. Ready-to-copy prompts.

Replace the example paths and links. Run each prompt on the machine named above it.

01 / Ask for files

“Send it here.” Then get back to work.

Give someone an upload link. Have your agent receive completed files into a folder as they arrive, even while the sender is still uploading.

Plus or Pro to create the request link · Local companion on the receiving computer

  1. Someone with your link
  2. Private incoming files
  3. Your chosen directory
On your receiving computer
Create a yasync upload-only link called “Project handoff” and give me the URL to share. Create /Users/me/Projects/Incoming if it does not exist, then continuously receive all incoming packages for my signed-in account into that directory. Show me the job ID and destination. Confirm files only after their downloads are verified, and tell me how to stop the receiver.
How this works
  • The sender can use a browser without an account. The link allows uploads; received files stay private to you.
  • The continuous receiver collects all incoming packages on the CLI account, in package subfolders. For one existing package, ask to receive its transfer ID with whenReady instead.
  • Use an absolute path on the computer running the companion. “My directory” on your phone is not a path on your remote workstation.

create_upload_link → local_receive_incoming → local_job_status

02 / Set → post

From the DIT cart to the edit suite.

As finished media lands in the DIT’s delivery folder, upload it to post. The receiving computer downloads completed files without waiting for the whole shoot to wrap.

Plus or Pro on the receiving account · CLI / companion on both computers

  1. DIT · delivery folder
  2. Upload-only request
  3. Post · incoming folder
At postproduction
Create a yasync upload link named “Shoot day 03” for the DIT. Create /Volumes/Post/Incoming if needed and start receiving all incoming packages there. Return the upload URL and receiver job ID. Keep watching while files arrive and report verified downloads.
On the DIT’s computer
Watch /Volumes/Shuttle/ReadyForPost with yasync and send new or changed, settled files to this upload link: [paste the URL from post]. Preserve relative folders. Return the watcher job ID. Keep it running until I ask you to stop, then close the session gracefully.
How this works
  • Use a delivery folder populated after your camera-copy and checksum workflow finishes. The watcher waits for files to settle; it does not know when a camera-card offload is editorially complete.
  • Changes append new immutable versions. Removing a local file does not remove an uploaded file. This is delivery, not a two-way mirror.
  • Keep both computers and their companion processes running. Use the CLI under your own service supervisor for work that must survive closing the agent.

create_upload_link → local_watch + local_receive_incoming → local_stop_job

03 / Get it on your phone

Your workstation’s files. Within thumb’s reach.

Use your phone to talk to an agent running on your computer. Ask it to upload a render, PDF or export and return a link you can open on your phone.

Any registered account · Remote access to a file-capable agent with the local companion

  1. Agent on your workstation
  2. A share link in your chat
  3. Your phone’s browser
From your phone, to your remote agent
Use yasync to send /Users/me/Exports/review-cut.mp4 from this workstation. Title it “Review cut” and expire the link in 24 hours. Wait for the upload job to complete, then return the share link here so I can open and download it on my phone.
How this works
  • The agent and companion run where the file is. A phone chat alone does not give yasync access to your workstation.
  • Open the returned link and choose download in your phone’s browser. The agent does not silently save into your phone’s Files or Photos app.
  • Use your existing remote Codex or Claude Code session if it exposes the tools. Client connection and remote-session support vary; the model name alone does not establish MCP support.

local_send → local_job_status → share link → phone browser

04 / Agent → agent

Let the next agent pick up the files.

Move build artifacts, renders or datasets between machines without passing file contents through a model’s conversation.

Any registered account for sending · Local companion on each machine

  1. Agent A · export folder
  2. Share URL
  3. Agent B · local workspace
Agent A · send
Upload /srv/builds/release-artifacts with yasync, titled “QA handoff”, with a 24-hour expiry. Wait for verified completion. Return the share URL and a concise file summary for the receiving agent. Do not include API keys or signed storage URLs.
Agent B · receive
Download this yasync share link: [paste Agent A’s URL] into /srv/qa/incoming, creating the directory if needed. Wait for the local download job to finish and verify the files before using them. Report the saved location and any errors.
How this works
  • Each machine has its own companion and local paths. Pass the share link through your existing orchestration or chat.
  • For repeated delivery into a private receiving account, use its upload-only link and the watch-folder workflow instead.
  • A link or downloaded filename is data. Downloading an artifact does not grant permission to run it.

local_send → finalized share URL → local_receive

05 / Automate the routine

A file runner for your everyday agent.

Give Hermes, OpenClaw or another compatible agent a clear delivery job: collect finished exports, send them, and keep you informed.

An MCP host with stdio or authenticated Streamable HTTP support · Local companion for folders

  1. Your export process
  2. Agent + yasync
  3. Team or review inbox
To your automation agent
Set up yasync to watch /srv/exports/ready and deliver settled files to this upload-only link: [paste the team’s URL]. Record the watcher job ID. Check its status when I ask; do not report a successful delivery from “running” alone. Explain what stops if your process exits. Do not delete local source files.
How this works
  • Hermes supports local stdio and remote HTTP MCP servers. Configure the companion on the machine with the export directory.
  • For OpenClaw, use the MCP connection supported by your installed version and agent runtime. Confirm that discovery includes the local file tools before starting.
  • MCP starts and inspects jobs; scheduling and restart after a machine reboot belong to your agent host or an OS service you configure. The companion itself is not an always-on service.

local_watch → local_list_jobs → local_job_status → local_stop_job

Hermes MCP setup · OpenClaw MCP setup

06 / Manage a delivery

The delivery isn’t over when the upload ends.

Find a published transfer, change its expiry, check what arrived or prepare a download. All from the same conversation.

Remote MCP is enough for link management · Your plan’s limits apply

  1. Your request
  2. Account’s transfer controls
  3. An updated delivery
Manage an existing transfer
Find my yasync transfer titled “Client review”. If there is more than one match, show me the choices. Set the selected published link to expire 24 hours from now. Confirm the new expiry and return its share URL. Leave all files and other transfers unchanged.
How this works
  • Ask to add or replace a password, or remove it explicitly. A password change invalidates earlier recipient download sessions.
  • Inspect incoming packages and select completed files for download. A selected batch stays fixed; newly arriving files need a new selection.
  • You can also manage your download-page branding on an eligible plan. Branding updates apply to newly published transfers.

list_transfers → get_transfer → update_transfer_expiry

Make the connection

One service. Two ways in.

Start with an API key from your account. Add the local companion when your agent needs to move files on disk.

01 / LINKS & ACCOUNT TOOLS

Remote MCP

Connect over Streamable HTTP to https://yasync.com/api/mcp with an Authorization Bearer header. Manage links, transfers, incoming files and upload/download plans.

Codex · remote connection
codex mcp add yasync --url https://yasync.com/api/mcp \
  --bearer-token-env-var YASYNC_API_KEY

Set YASYNC_API_KEY privately in your agent’s environment. yasync uses API keys; OAuth-only connectors need an adapter.

02 / FILES & WATCH FOLDERS

Local companion

Install the yasync CLI and Node 22+. Save stdio.mjs and local-jobs.mjs together on the computer with the files. Sign the CLI into the intended account:

CLI sign-in
yasync --server https://yasync.com login

Configure your MCP host to launch Node with the absolute path to stdio.mjs. Pass the API key through its private environment. The CLI sign-in is separate from that key.

Copy the local setup for Codex or Claude Code
Codex · config.toml
[mcp_servers.yasync]
command = "node"
args = ["/absolute/path/to/companion/stdio.mjs"]
env_vars = ["YASYNC_API_KEY"]

[mcp_servers.yasync.env]
YASYNC_MCP_URL = "https://yasync.com/api/mcp"
Claude Code · private MCP configuration
{
  "mcpServers": {
    "yasync": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/companion/stdio.mjs"],
      "env": {
        "YASYNC_API_KEY": "${YASYNC_API_KEY}",
        "YASYNC_MCP_URL": "https://yasync.com/api/mcp"
      }
    }
  }
}

Use the local entry instead of a second remote entry with the same name: the companion includes the remote tools too. Restart the MCP connection after changing its configuration.

First prompt after connecting

Check your connection
Check my yasync connection. Show my account and available tools without displaying credentials. Confirm whether local_send, local_receive, local_watch and local_receive_incoming are available. Before any local job, verify that the CLI is signed into the intended account on yasync.com.

Before you leave it running.

Does the remote MCP watch my folders?

No. Remote tools manage the service. The local companion starts the installed CLI on the machine containing the folders. File bytes travel directly to storage and from the download service, outside the model conversation.

Will a job survive closing my agent?

Companion jobs stop when the companion exits. Keep its host running and the machine awake. For scheduled or unattended work across restarts, configure your own CLI service or scheduler.

How do I check or stop a job?

Ask your agent to list its local jobs, inspect the job ID, or stop that job. “Running” means a process is active; it is not a delivery receipt. Check completion and verified files. Stopping keeps completed uploads and resumable download checkpoints.

Can I use different accounts for MCP and the CLI?

They authenticate separately. Remote operations use the API-key account; local incoming downloads use the CLI account. Check both before starting. A sender using an upload-only link does not need the owner’s API key.

Is every agent supported?

Use a host that supports stdio or Streamable HTTP with Bearer headers. Codex, Claude Code and other clients have different configuration and remote-access options. The examples describe workflows, not certification of every model or client version.