Upload a local file to Sume from chat: hosted MCP can't read disk

You attach a product photo in a chat and ask for a video. The model calls Sume's tools, which run on a server, and the server has no access to your laptop. The MCP tools and gates page says it directly: hosted MCP cannot read files from your laptop.

The three steps

• Call assets_upload_url (write tool, needs idempotency_key) to get an upload URL.
• The client PUTs the file bytes to that URL.
• Call assets_complete (write tool) to finish the asset, then use the asset in a generation call.

If your chat client cannot PUT

Some chat surfaces cannot make an HTTP PUT with your attachment. Then use a URL that Sume can fetch: media-imports_create mirrors a social or public URL, and read tools such as assets_get and assets_download_url show what is stored. Because upload tools are write tools, a read-only OAuth session will not list them; see the Write toggle in OAuth and API keys.

Keep the links clean

The tools page prefers Sume public ids and media.sume.com URLs in reports, and says not to paste signed URLs, OAuth tokens or API keys into chat logs. An upload URL is a signed URL: use it once, and do not put it in a transcript you will share.

If you need the same photo across many runs, upload it once, keep the asset id, and reuse it, which also keeps scheduled or cloud-run jobs from depending on a local path.