@productmaker/mcp 2.8.3 → 2.9.2

package/README.md

@@ -86,7 +86,7 @@ Sign up at [productmaker.app](https://productmaker.app) and create a key (prefix
 | `list_shopify_products` | Search products in a connected Shopify store before choosing `targetProductId` for `publish_to_shopify` |
 | `list_meta_ad_accounts` | List connected Meta ad accounts |
 | `list_meta_destinations` | List Meta Business portfolios, ad accounts per portfolio, and Facebook Pages; use the returned IDs to choose the exact publication destination |
-| `request_meta_media_upload` | Create a one-click ProductMaker upload page for up to ten mixed image/video files on the user's laptop; ChatGPT may attach optional `files` references for the UI bridge, but the MCP never downloads them and still uses the secure ProductMaker page |
+| `request_meta_media_upload` | Start secure staging for up to ten mixed image/video files from the user's laptop; accepts an optional `maxFiles` limit, ChatGPT can pass optional top-level `files` references from the same message into the inline App bridge, other MCP App hosts use the inline picker, and the external ProductMaker page remains fallback only |
 | `check_meta_media_upload` | Check whether the user finished the browser upload and return every owner-scoped staged asset with its media kind |
 | `list_tiktok_advertisers` | List connected TikTok Ads advertiser accounts |
 | `publish_to_shopify` | Publish a completed task to a Shopify store (returns markdown with landing + product URLs) |
@@ -106,13 +106,19 @@ Sign up at [productmaker.app](https://productmaker.app) and create a key (prefix
 ### Uploading personal media from a remote chat
 
 When a user says “sube estos archivos de mi Desktop a Meta”, the hosted MCP
-cannot open the laptop filesystem. Call `request_meta_media_upload` with its
-default `mediaKind: "mixed"`; it returns a secure one-click ProductMaker page
-for up to ten images and videos. In ChatGPT the tool may also receive top-level
-`files` references from the host, but ProductMaker treats them only as UI
-bridge metadata: it never downloads those URLs and it still requires the user
-to complete the secure upload page. Ask the user to select the files there,
-then call `check_meta_media_upload` with the returned `sessionId`. For every
+cannot open the laptop filesystem directly. Call `request_meta_media_upload`
+with its default `mediaKind: "mixed"`. The primary path is the inline MCP App:
+in ChatGPT, the same user message may contribute top-level `files` references;
+in other MCP App hosts, the user can still pick the files from the inline
+widget. The inline device picker sends `File` objects directly to ProductMaker's
+private staging CDN; it does not upload them to the host first. ProductMaker
+treats any `files` references only as UI bridge metadata:
+it never downloads those URLs itself, never forwards them to the API, and never
+asks the user for a CDN URL, local path, bytes, or base64.
+
+If the host lacks the bridge/picker capabilities, fall back to the external
+ProductMaker upload page returned by the tool. Once the user finishes staging,
+call `check_meta_media_upload` with the returned `sessionId`. For every
 reported entry in `assets[]`, use its `mediaKind` as the creative `type` and
 its `stagingAssetId` as: