Send files with Codex and yasync
Connect Codex to yasync MCP with a Bearer key, inspect transfers, and send local files using the yasync CLI.
Remote MCP with an environment-based Bearer key; CLI for local files.
Connect your file workflow
Practical guides for using yasync with Codex, Claude, Grok and ChatGPT. Choose the connection your client supports, check it with an existing transfer, then add file delivery.
API keys, MCP and the CLI require Pro. The desktop app and browser remain available on every tier. Uploading local files needs a client with file access; connecting MCP alone does not move bytes from your disk.
Transfer files with Claude Code and yasync
Configure Claude Code HTTP MCP for yasync, inspect delivery status, and upload approved local files with the CLI.
Claude Code HTTP MCP with environment-variable headers.
Connect Grok to yasync file transfers
Use xAI remote MCP tools to inspect yasync transfers from a Grok API workflow, with explicit authentication and read-only tool selection.
xAI Responses API remote MCP; separate xAI and yasync credentials.
Use yasync with ChatGPT file workflows
Build a private ChatGPT GPT Action for the yasync REST API, list existing transfers, and understand the limits of native MCP and local file uploads.
Private GPT REST Action with API Key / Bearer authentication; MCP needs an authenticated adapter.