picsart-add-media

# Add Media (Upload Widget) Picsart's MCP tools take **URLs**, not local paths, and most agent hosts (browser-based chats, Claude Code without shell access, ChatGPT web) can't read a file straight off the user's disk either. The fix is a browser-based **upload widget**: an MCP tool opens a drag-and-drop panel in the user's browser, the browser uploads the file directly to Picsart's CDN, and the widget hands the resulting URL back to you. No file bytes ever pass through a tool call. ## When to Use Fires on things like "I have 3 video clips", "here are my photos", "use my footage", "combine these clips" — anything where the media is the user's own and you don't already have a link to it. Reach for this whenever the next step needs a URL (`image_url`, `video_url`, `startFrame`, …) and the source is something on the user's own machine, a chat attachment you can't fetch, or anything else not already a public `https://` link. ## Prerequisites A Picsart MCP connector present in the current tool list. This skill calls whichever of these is connected: - **`picsart_upload_widget`** — on the Picsart MCP connector (tools prefixed `picsart_*`). This variant also offers a "Save to Drive" option and a Drive-browsing tab, because that connector has Drive access. - **`mp_upload`** — on the Picsart media-tools connector (tools prefixed `mp_*`). This variant has no Drive integration; its second tab is "Use existing" (picks from `known_urls` you pass in), not a Drive browser. If ...