Signed media resources in an MCP generation workflow

Choose the next page by the boundary you still need

Return to the MCP image-generation learning center when you need the broader relationship among tools, authorization, generation state, and outputs. Use the human-in-the-loop payments page when the next uncertainty is who may approve spend rather than who may read media. Use the rate-limits page when retrieval is failing because of request pacing rather than an expired delivery capability. This page owns only signed media delivery and does not replace those protocol, payment, or operations guides.

Separate the storage grant, delivery route, and MCP result

A signed media URL is a delivery capability, not evidence that the underlying object is public. Cloudflare documents an R2 presigned URL as a signature-bearing bearer token for one object, one operation, and a bounded expiry. Supported operations include GET, HEAD, PUT, and DELETE, and the configured lifetime can range from one second to seven days. Possession is sufficient while the link remains valid, so the URL itself must be handled like a temporary credential.

Public hosting is a different R2 configuration. R2 buckets are private by default, while public access must be explicitly enabled through a custom domain or an `r2.dev` development URL. Cloudflare also states that S3 presigned URLs work only on the R2 S3 API domain, not on custom domains. A product may instead keep R2 behind its application and issue an application-origin signed route. Readers should therefore inspect the actual URL and product documentation rather than calling every expiring media link an R2 presigned URL.

MCP adds a third boundary. The current MCP resource specification uses URIs to identify resources and says an HTTPS resource URI should be used only when the client can fetch it directly. OfflineCreator's current public MCP package takes a narrower product approach: completed generation tools return a Studio-origin `outputUrl`, content type, and expiry metadata in a text JSON result. The package describes that URL as short-lived and says `download_output` does not stream media bytes into model context.

Storage

Private object in R2Private storage and public bucket exposure are separate configuration choices.

Delivery

One temporary URL with scheme-specific rulesNative R2 presigned URLs are bearer tokens; the retrieved sources do not establish identical redemption behavior for every product-signed route.

MCP result

Metadata that lets the client retrieve mediaA URL returned inside a tool result is not automatically an MCP resource registration or a public asset.

Authorize first and keep the durable generation identity

The durable handle in a generation workflow should be the generation ID, not a copied download URL. OfflineCreator's published server maps `get_generation`, `wait_generation`, `download_output`, and `list_generations` to its read scope. Its API-key client adds an `Authorization: Bearer` header, requests only `/api/v1/` paths, refuses unexpected redirects, and omits an output URL it cannot constrain to the configured Studio origin. These package-side checks do not prove how every backend ownership decision is implemented.

Use the returned `outputUrlExpiresAt` or `outputUrlExpiresInSeconds` as control data and download before the stated expiry. Do not edit a native R2 presigned URL's query parameters: Cloudflare documents that the embedded signature authorizes a specific S3 operation on a specific object until expiry, so treat the complete URL as an opaque bearer token rather than a mutable path. That guidance is specific to R2's Signature Version 4 URLs. The retrieved OfflineCreator sources show that `get_generation` and `download_output` request current generation data, but they do not establish that repeating either call always mints a different or newly valid URL.

OfflineCreator's privacy policy says account authorization is required to mint a signed download link. Cloudflare separately states that a native R2 presigned URL needs no additional authentication header and must be treated as a bearer token. The retrieved sources do not establish that OfflineCreator's Studio-origin route has the same redemption semantics, so this page does not claim that its link works without account authentication. Keep the complete returned URL out of durable records regardless of the undisclosed redemption details.

Durable reference

generationIdStore the job identifier so an authorized client can request current status without treating an expiring URL as durable identity.

Ephemeral reference

outputUrl plus expiry metadataUse it for the immediate transfer and discard it from prompts, tickets, analytics, and long-lived manifests.

Stale-link path

Do not assume undocumented renewal behaviorRecheck current product documentation or support guidance; the reviewed package does not promise that another call returns a newly valid URL.

Keep bearer URLs out of model context and durable telemetry

A signed URL can expose authorization parameters in its query string. Cloudflare explicitly says to treat R2 presigned URLs as bearer tokens and share them only with intended recipients. Do not place the complete URL in prompts, screenshots, issue titles, analytics events, referrer-bearing pages, or logs that outlive the transfer. Redact the query string when recording a diagnostic and store the generation ID, content type, expiry timestamp, and transfer result instead.

OfflineCreator's privacy policy says Studio media is private by default, signed download links expire quickly, and account authorization is required to mint them. It also says an explicit Community publication makes that generation's media, prompt, and settings public until unpublishing. Those are separate distribution choices: copying an owner download URL is not the publication workflow, and publishing is not a way to repair an expired owner link.

The link's expiry does not establish that the stored object was deleted, that every downstream copy vanished, or that a recipient never downloaded it. OfflineCreator states that generation history and media remain until the user deletes them or closes the account, subject to backup windows. Apply deletion and retention controls to the underlying generation separately from delivery-link expiration.

Safe record

Generation ID, MIME type, expiry, and resultThese fields support retry and audit without preserving a usable bearer token.

Unsafe record

Full signed query stringRedact it before logs, screenshots, support threads, model prompts, or analytics.

Deletion

Separate object lifecycle actionURL expiry, unpublishing, and deleting stored media solve different problems.

Keep signed delivery distinct from public hosting and MCP resources

This page owns the query “mcp signed media urls”: how an MCP tool result can hand a client expiring delivery metadata, why a native R2 presigned URL is sensitive, and why temporary delivery does not by itself make private storage public. It does not claim that every MCP server uses R2, that every signed URL uses AWS Signature Version 4, or that a URL serialized in tool-result text is automatically a listed MCP resource. The official tools specification permits resource links, while the reviewed OfflineCreator package currently serializes its output metadata as text JSON.

Research limitation: the required recent-evidence run had degraded source coverage. Optional X/Twitter credentials were not configured, Reddit returned only a partial lane after RSS failures, and the 75 retrieved items did not substantiate OfflineCreator signed-delivery outcomes, numeric URL lifetimes, or practitioner consensus for this page. The single relevant hit was Cloudflare R2 upload documentation adjacent to signing behavior; remaining material was marginal protocol news, promotional MCP demos, or off-topic. These are provenance disclosures, not evidence claims about signing behavior; no retrieved community item or engagement metric supports page guidance.

Public-evidence limitation: primary documentation supports the R2 and MCP distinctions, and the published product package supports only the tool/result behavior attached to ledger claims on this page. The retrieved public sources do not state OfflineCreator's numeric URL lifetime, promise URL renewal from `get_generation` or `download_output`, document per-link rotation, or establish whether the Studio-origin link can be redeemed without account authentication. Keep the route unpublished and preserve those unknowns until exact public evidence or an approved live test closes them.