"Dropbox" matching MCP tools:

• score_my_videoA

  AINSOFA

  Create a watermarked music-scored MP4 from a supported video URL and an English music brief, an explicit catalogue track, or timed sections. Measures video duration and edit pace, selects or uses the specified music, and mixes it with the source audio. Sections support separate cues, versions or stems; silences specify music-free intervals. Section and silence boundaries are adjusted to measured shot boundaries. Returns video download/watch links, chosen cues, mix details, duration and shot-count summary. Detailed cut timestamps, storyboard frames and transcripts are provided by analyze_video, not this tool. Completed delivery packages are retrieved with deliver_score using the scoring arguments. Supports direct video files and supported Dropbox/Google Drive shares; stream-only YouTube, Vimeo, Dailymotion and Twitch pages are unsupported. Creates private processing jobs and stored outputs. After verified output storage, the temporary AINSOF-uploaded source copy is deleted or queued for deletion retry; the local original is unchanged. Processing may return still_running; recent identical requests reuse existing work. Terminal failures return a reason.

  Connector

  Destructive

  No auth

• score_my_videoA

  AINSOFA

  Create a watermarked music-scored MP4 from a supported video URL and an English music brief, an explicit catalogue track, or timed sections. Measures video duration and edit pace, selects or uses the specified music, and mixes it with the source audio. Sections support separate cues, versions or stems; silences specify music-free intervals. Section and silence boundaries are adjusted to measured shot boundaries. Returns video download/watch links, chosen cues, mix details, duration and shot-count summary. Detailed cut timestamps, storyboard frames and transcripts are provided by analyze_video, not this tool. Completed delivery packages are retrieved with deliver_score using the scoring arguments. Supports direct video files and supported Dropbox/Google Drive shares; stream-only YouTube, Vimeo, Dailymotion and Twitch pages are unsupported. Creates private processing jobs and stored outputs. After verified output storage, the temporary AINSOF-uploaded source copy is deleted or queued for deletion retry; the local original is unchanged. Processing may return still_running; recent identical requests reuse existing work. Terminal failures return a reason.

  Connector

  Destructive

  No auth

• sprkly_add_media_from_urlA

  sprkly-mcpA

  Download an image or video from a public link into sprkly and get a media_id back, for reuse across several posts. You usually do NOT need this: sprkly_schedule_post accepts a link directly in media_urls and pulls it into storage itself whenever the target platform requires that. Reach for this tool only when the user wants one media_id to attach to more than one post. Google Drive and Dropbox share links are converted automatically; the file must be shared publicly. Limit 50 MB.

  ConnectorNo auth

• sprkly_add_media_from_urlA

  sprklyA

  Download an image or video from a public link into sprkly and get a media_id back, for reuse across several posts. You usually do NOT need this: sprkly_schedule_post accepts a link directly in media_urls and pulls it into storage itself whenever the target platform requires that. Reach for this tool only when the user wants one media_id to attach to more than one post. Google Drive and Dropbox share links are converted automatically; the file must be shared publicly. Limit 50 MB.

  ConnectorNo auth

• submit_videoA

  OpenClipA

  Submit a source video `url` (YouTube, Vimeo, Google Drive, Dropbox, OneDrive, Rumble, or a direct video file) to turn into viral clips, with an optional `title`. Returns the new video `id` (a hashid) and its `status`. Processing is ASYNCHRONOUS: this returns `status: "downloading"` or a paused `pending_credits` state. Poll get_video_status with the returned `id` while processing moves. Do not poll `pending_credits`: when a failed payment caused the pause, the result includes `payment_required: true`, a message, and `billing_url`; show that guidance so the user can repair payment. Optionally pass an `agent` id (a hashid from list_agents) to process the video with that agent's settings (caption preset, composition defaults, …); omit it to use the team's defaults. Optionally pass `max_clip_seconds` (15 to 90) to cap how long each clip runs (omit it for automatic lengths, 40 to 90 seconds), and `clip_guidance` (up to 300 characters) to say which moments to prefer, for example "only the funniest reactions". Guidance that is too narrow or not about picking moments is rejected with a reason and a broader suggestion. Safe to retry: submitting the same url + agent + clip preferences again returns an existing run for it from the last 24h (still processing, or completed) as `deduped: true` instead of starting a second run. Submitting the same url with a DIFFERENT agent or clip preferences starts a new run (so you can re-process a source with other settings). A previously *failed* url can be resubmitted to retry it. Errors: an unsupported/invalid URL is rejected and an agent not on your team is rejected. A missing subscription or insufficient credits parks the video in `pending_credits`; direct the user to OpenClip before checking again.

  ConnectorOAuth

• convert_from_urlA

  BotverseA

  Offload a document conversion to Botverse — runs server-side in seconds, returns a download link, and frees you to continue with other tasks while it processes. Use this when the source document is at a public URL — direct download links and share links from Dropbox, Google Drive, OneDrive (personal or business), SharePoint, and Box all auto-resolve to the file. If you already have the content as a string, use convert_content instead — no upload step needed. Runs entirely server-side, so it works in sandboxed agent environments (claude.ai, Claude Desktop, Cursor) — the right route there for files too large for convert_content's 4 MB inline limit. Supported inputs: md, html, rst, txt, docx. Supported outputs: docx (Word), pdf, html, txt, md, rst, xlsx (tables extracted). Returns a job_id immediately. Poll get_job_status every 5s until 'complete', then get_output_content (inline, sandbox-safe) or get_download_url (download link). Flat fee $0.05 per file.

  ConnectorNo auth

• vivid_artworkA

  vivid-ads-commerceA

  Attach a customer-provided artwork file or link to a signage order (a successful attach does NOT mean it is print-ready — the team still checks it). EASIEST: pass a shareable link to the file (sourceUrl) — Google Drive, Dropbox, WeTransfer, etc. — and use the returned fileUrl in vivid_place_order's artwork {mode:'upload_file', fileUrl}. For a large file with no link yet, set requestUpload:true to get a direct-upload URL (the file uploads straight to storage — handles 50–200MB+), then call again with the returned fileId to get the share link.

  ConnectorNo auth

• extract_contract_from_urlA

  transaction-coordinatorA

  Extract structured transaction data from a contract at a URL. Downloads the document, extracts text (with OCR fallback for scanned PDFs), and runs PrimaCoda's contract-extraction prompt to return parties, addresses, dates, prices, and key contract fields. Use this when an agent has the contract hosted somewhere (Dropbox, Google Drive direct download, Square Space, etc.) and wants to skip the upload step. For multi-document deals (purchase + addenda + disclosures), use the PrimaCoda dashboard's batch upload — this tool handles ONE document. Args: pdf_url: Direct download URL for the contract (PDF, DOCX, TXT, or image). Must be reachable from the PrimaCoda server. Google Drive "shared link" URLs work if set to "anyone with link"; other share URLs may need their direct-download form. api_key: Your PrimaCoda MCP API key (starts 'pck_').

  ConnectorNo auth

• reset_connector_tokenA

  CorpusIQC

  Reset connector auth state for the current user. Use when tokens are stale, missing scopes, tied to the wrong account/workspace, or repeatedly failing auth. For credential-based connectors, this clears the saved credentials so the user can re-enter them. Input: connector_id (required). Supported values: google_workspace, microsoft, dropbox, shopify, shopline, quickbooks, hubspot, slack, ebay, facebook_marketing, tiktok, klaviyo, calendly, activecampaign, odoo, constantcontact, airtable, gohighlevel, monday, semrush, ahrefs, posthog, stripe, gunbroker.

  Connector

  Destructive

  No auth

• uploadStayPhotoA

  Nomad StaysA

  Upload a photo to one of your Stay's photo areas. Supply EXACTLY ONE of 'url' (a public https:// link, e.g. a Google Drive or Dropbox share link — the server downloads it) or 'base64' (the raw image bytes, base64-encoded — use this when you already have the image data in hand, e.g. a user attached a photo in the conversation, and have nowhere public to host it first). The photo is validated against the same minimum specs as a manual upload: JPEG, PNG, or WebP, under 20MB, and a minimum resolution that depends on area. Most areas require at least 1920x1080 landscape; 'host' requires at least 1080x1350 PORTRAIT — a landscape photo will be rejected for that area. Every upload is downscaled to fit within 2560x1440 and re-encoded server-side as WebP (stripping metadata and anything that isn't genuine image data) before storage. Requires NOMADSTAYS_MCP_AGENT_TOKEN.

  ConnectorNo auth

• check_mediaA

  Adako: Google Ads, Meta Ads & Linkedin Ads MCPA

  🟢 READ-ONLY — runs immediately, changes nothing. Cost: free (not counted against tasks). Checks a creative file before any ad is built from it, and answers where a file with no link yet has to go. Use when: the user offers an image or a video in any form — a link, a file on their computer, "the one from our site" — and always before a create tool that takes image_url or video_url. What it does: repairs the share links that do not serve files (Drive, Dropbox, OneDrive, GitHub, Imgur have a direct form), fetches only the head of the file to read its type, size, dimensions and an MP4's duration, and reports slot by slot which platforms accept it and what would be cropped. Call it with no arguments when the user has a file but no link: it returns the three ways to get one, cheapest first, starting with reusing what is already in their ad account. Adako hosts nothing and never receives the file. The platform downloads the URL itself, from its own servers and often hours later, which is why a local path, a login-gated page or a link that expires cannot work however it is passed. Free, instant, touches no ad account and creates nothing, so run it as often as needed. If a file is refused, say exactly which rule it broke and what to change — never retry a create with the same file.

  ConnectorOAuth

• popcraft_media_uploadA

  PopcraftA

  Get upload URLs for a local image/video/audio file that has no public URL to hand to `popcraft_media_import_url`. THIS IS THE TOOL FOR VIDEO and for anything over 20 MB. Returns a `proxy_upload_url` on Popcraft's OWN host (PUT the bytes there — total file size up to the per-type cap: video 500 MB, image 30 MB, audio 50 MB; each individual REQUEST is capped at 28 MB by the transport, so files over 28 MB use the chunked recipe B — same URL, same total cap) and an `upload_url` for a direct PUT to storage.googleapis.com (fewer hops, but a different host that sandboxed clients often cannot reach). The result text contains ready-to-run shell recipes including the chunked one for large files — RUN one of them rather than reimplementing the upload. Running a shell command also keeps the file bytes out of your context, which is why this beats `popcraft_media_upload_inline` for video: that tool needs the whole file base64-encoded in its arguments, so it is only practical for small files. CAUTION on platform-mediated clients (e.g. claude.ai connectors): tool calls are made from the platform's servers, so this call succeeding does NOT prove your shell can reach Popcraft — run the 5-second egress probe in recipe 0 first. If your shell's egress is blocked: prefer asking the user for any shareable link to the file (Drive/Dropbox/etc) and `popcraft_media_import_url` (server-side fetch, immune to client egress blocks); if no link exists, open `popcraft_media_upload_widget` when the client renders widgets. After the upload, call `popcraft_media_confirm` with the returned `media_id` to verify it landed, then pass that `media_id` as a `medias[].value` for `popcraft_generate_image` / `popcraft_generate_video` / `popcraft_generate_audio`. If you have no shell and no network at all, fall back to `popcraft_media_upload_inline` — but never tell the user to upload the file on the website instead.

  ConnectorOAuth

• popcraft_media_upload_widgetA

  PopcraftA

  Open an interactive file-picker widget for the user to upload an image/video/audio file directly into Popcraft — use this instead of `popcraft_media_upload` when the client can render MCP Apps widgets and the user should pick/drag a file themselves, or when your shell's egress is blocked (sandboxed client) so the upload recipes cannot run. BEFORE opening it, check the one zero-click alternative: if the file exists anywhere online (Google Drive, Dropbox, any share link), ask the user for the link and use `popcraft_media_import_url` instead — Popcraft fetches it server-side, so client egress does not matter and the user never has to click anything. The widget uploads from the user's BROWSER, so it works even when both your shell and the user's machine cannot PUT to Popcraft directly. It drives the upload end-to-end (signed URL, PUT, confirm) and, once confirmed, hands the resulting `media_id` back as the next user message so you can use it as a `medias[].value` for `popcraft_generate_image` / `popcraft_generate_video` / `popcraft_generate_audio`. Pass `type` and a specific `label` naming the exact file you expect.

  ConnectorOAuth

• popcraft_media_uploadA

  PopcraftA

  Get upload URLs for a local image/video/audio file that has no public URL to hand to `popcraft_media_import_url`. THIS IS THE TOOL FOR VIDEO and for anything over 20 MB. Returns a `proxy_upload_url` on Popcraft's OWN host (PUT the bytes there — total file size up to the per-type cap: video 500 MB, image 30 MB, audio 50 MB; each individual REQUEST is capped at 28 MB by the transport, so files over 28 MB use the chunked recipe B — same URL, same total cap) and an `upload_url` for a direct PUT to storage.googleapis.com (fewer hops, but a different host that sandboxed clients often cannot reach). The result text contains ready-to-run shell recipes including the chunked one for large files — RUN one of them rather than reimplementing the upload. Running a shell command also keeps the file bytes out of your context, which is why this beats `popcraft_media_upload_inline` for video: that tool needs the whole file base64-encoded in its arguments, so it is only practical for small files. CAUTION on platform-mediated clients (e.g. claude.ai connectors): tool calls are made from the platform's servers, so this call succeeding does NOT prove your shell can reach Popcraft — run the 5-second egress probe in recipe 0 first. If your shell's egress is blocked: prefer asking the user for any shareable link to the file (Drive/Dropbox/etc) and `popcraft_media_import_url` (server-side fetch, immune to client egress blocks); if no link exists, open `popcraft_media_upload_widget` when the client renders widgets. After the upload, call `popcraft_media_confirm` with the returned `media_id` to verify it landed, then pass that `media_id` as a `medias[].value` for `popcraft_generate_image` / `popcraft_generate_video` / `popcraft_generate_audio`. If you have no shell and no network at all, fall back to `popcraft_media_upload_inline` — but never tell the user to upload the file on the website instead.

  ConnectorOAuth

• popcraft_media_upload_widgetA

  PopcraftA

  Open an interactive file-picker widget for the user to upload an image/video/audio file directly into Popcraft — use this instead of `popcraft_media_upload` when the client can render MCP Apps widgets and the user should pick/drag a file themselves, or when your shell's egress is blocked (sandboxed client) so the upload recipes cannot run. BEFORE opening it, check the one zero-click alternative: if the file exists anywhere online (Google Drive, Dropbox, any share link), ask the user for the link and use `popcraft_media_import_url` instead — Popcraft fetches it server-side, so client egress does not matter and the user never has to click anything. The widget uploads from the user's BROWSER, so it works even when both your shell and the user's machine cannot PUT to Popcraft directly. It drives the upload end-to-end (signed URL, PUT, confirm) and, once confirmed, hands the resulting `media_id` back as the next user message so you can use it as a `medias[].value` for `popcraft_generate_image` / `popcraft_generate_video` / `popcraft_generate_audio`. Pass `type` and a specific `label` naming the exact file you expect.

  ConnectorOAuth

• import_from_google_driveA

  PlaybookA

  Import Google Drive folders into a board. Use this for files that live in the user's Google Drive, including private folders — upload_from_url cannot reach those. Google Drive and Dropbox are connected ONCE, by a person, in the Playbook web app — there is no tool that connects them. Connections belong to a Playbook user: this server only sees connections made by the same Playbook account it is signed in as. When list_import_sources has no source with the needed `provider`, its `connect_url` is where a person connects that service; the source is listed once they have. Every folder is checked against the connected Google account first; one it cannot see is refused with the account's email, which usually means the folder must be shared with that account. RE-SYNC: importing the same folder into the same `board_token` skips files already there unchanged, so a recurring sync should reuse the board. But a file changed in Drive is added as a SECOND asset next to the old one, and renaming the Drive folder or its sub-board imports that folder again in full. WHERE FILES LAND: each folder becomes a sub-board NAMED AFTER THE FOLDER inside the target board, with its sub-folders nested below — not the target board itself. Find it with list_board_children on `board_token`, or list_assets with nested_assets. The import is ASYNCHRONOUS: this returns a run in `pending`; poll get_import until `status` is `completed` or `canceled`. Plans without unrestricted imports allow one active import per workspace; the refusal names the active import's token, so poll that instead of retrying. Storage overage cannot be agreed to here: the call is refused when the workspace has no storage left before overage it has not agreed to, and the import is canceled (`overlimit`) before storing a file that would cross it. A rate-limit error carries a retry delay — wait that long. Requires a `write`-scope token and workspace owner/admin permission.

  ConnectorOAuth

• transcribe_from_urlA

  BotverseA

  Transcribe a video or audio file from a public HTTPS URL into a speaker-labelled transcript — ONE call does everything. Source can be a direct HTTPS URL or a share link from Dropbox, Google Drive, OneDrive (personal or business), SharePoint, or Box — share links auto-resolve to the file. Internally: converts to audio, runs speech-to-text with speaker diarization, uses AI to name the speakers from your attendee list, and renders the document. Pass `options.attendees` (names, optional gender/role) and it tags who said what. Output formats: txt, json, srt, vtt, docx, pdf. CONSENT: you must have all parties' consent to record/transcribe — Botverse accepts no liability otherwise. Returns a job_id immediately — report it to the user, then poll get_job_status (it reports a live stage: converting audio → transcribing → AI augmenting → rendering) until 'complete', then get_download_url (or get_output_content for inline bytes in a sandbox). ~$3 per hour of audio. RELIABILITY & FALLBACK: Botverse returns structured errors with a message. A bare 'HTTP 500' or 'tool call failed' with no message body is the MCP connector / sandbox layer between your client and Botverse — NOT a Botverse outage (the service is up if get_wallet_balance succeeds). If MCP calls keep failing, do NOT write your own ffmpeg / transcription / document-conversion code as a workaround — that wastes tokens and reinvents what Botverse does. Instead, tell the user to run the equivalent Botverse CLI from their own (non-sandboxed) machine, e.g. `npx botverse transcribe <file> --to docx` (also `transcode` and `convert`), then retry the MCP call.

  ConnectorNo auth

• check_printabilityA

  FabTally 3D-Print Slicer, Quote & DFMA

  FREE 3D-printing DFM / printability check for an STL/3MF/OBJ/PLY model. Paste a link: Thingiverse/Printables/MakerWorld model pages, a GitHub blob, Google Drive or Dropbox share link, a direct .stl/.3mf/.obj/.ply/.step URL, or a .zip (first printable model inside is used). Local file? Upload once at https://fabtally.com/upload and paste that URL. Default (full=false): a fast geometry-only read — printable verdict (yes/with-warnings/no), watertight/manifold, dimensions & volume, fits-on-bed, wall-thickness estimate vs the 0.4mm nozzle, overhang heuristic. Set full=true for the complete report with EXACT support-material grams/time and infill material-saving deltas from REAL slices (every field labelled exact vs heuristic). Both are FREE for personal/interactive use (fair-use limits); agents/high-volume use prepaid credits or the x402 lane.

  ConnectorNo auth

• media_from_urlA

  uplikaA

  Attach an image or video that is already on the public web. We download it, copy it into our storage and give you a media id you can pass to publish. One step, no upload needed. https only. Google Drive and Dropbox **share** links do not work: they return an HTML preview page, not the file. Use a direct file URL that ends in the file itself. Accepted formats (read from the bytes, not the headers): image/jpeg, image/png, image/gif, image/webp, video/mp4, video/quicktime. Each channel then checks what it takes when you publish. If you can see the image, write altText describing it.

  ConnectorNo auth

• create_comment_to_dmA

  uplikaA

  The most common automation: when someone comments on a post, DM them. **Creates a draft; nothing goes out until enable_automation.** How Meta works: a DM cannot be started by the account. The only automatic door is a private reply to a comment, one per comment, within 7 days of the comment, and once the person answers the 24-hour window opens for the rest. Instagram can check whether the person follows the account (requireFollow); Facebook cannot, so requireFollow is rejected there. Threads has no DMs at all; use create_automation with comment_public_reply. A file to deliver: if it already has a public https link that returns the file itself (jpeg, png, gif, webp, mp4, mov or PDF), pass it as deliver.fileUrl and it goes to the person as-is; the link is opened once on save and a web page (a Google Drive or Dropbox share page), a private address or a dead link is rejected. If the file has no public link, upload it to Uplika first (media_upload_link without a shell, media_presign then media_complete with one) and pass deliver.mediaId (photos, videos, PDF or HWP/HWPX documents; on Instagram a document other than PDF goes as a download link, because Instagram DMs attach PDF only). Not both. post can be our post id, the post's own id on the platform, a link to the post, "any" for every post, or "next" for the next post you publish (or pass automation on publish to do both in one call). Only one enabled automation per account can wait for "next" (409 next_post_taken). Order when everything is on: opening DM (message + button) -> askEmail -> requireFollow -> deliver (text, up to three link buttons, file; clicks are tracked) -> followUp if no link was clicked. openingDm:false sends deliver as the private reply itself; then requireFollow, askEmail, followUp and files are rejected because the window never opens. The optional public reply under the comment is fixed sentences (publicReply) or written by the AI for each comment (publicReplyMode: "ai" with publicReplyInstruction); either way it is posted only after the private reply went out, and the AI is told a DM was sent.

  ConnectorNo auth

• transcode_from_urlA

  BotverseA

  Offload a video or audio transcode to Botverse using a public URL — no upload step needed. Accepts a direct HTTPS download URL, or a share link from Dropbox, Google Drive, OneDrive (personal or business), SharePoint, or Box — share links auto-resolve to the file. Also works with any direct HTTPS download URL (CDN, S3, etc.). Limited to 2 GB. Returns a job_id immediately. IMPORTANT: tell the user the job_id right away so they can track it. Then poll get_job_status every 5 seconds. Large video files (>100 MB) can take 5–15 minutes — keep polling until status is 'complete' or 'failed', no matter how many polls it takes. Never give up early. Wallet debited on completion. Use options.start_time and options.duration to trim — e.g. start_time='00:01:00', duration=120 for a 2-minute clip. RELIABILITY & FALLBACK: Botverse returns structured errors with a message. A bare 'HTTP 500' or 'tool call failed' with no message body is the MCP connector / sandbox layer between your client and Botverse — NOT a Botverse outage (the service is up if get_wallet_balance succeeds). If MCP calls keep failing, do NOT write your own ffmpeg / transcription / document-conversion code as a workaround — that wastes tokens and reinvents what Botverse does. Instead, tell the user to run the equivalent Botverse CLI from their own (non-sandboxed) machine, e.g. `npx botverse transcribe <file> --to docx` (also `transcode` and `convert`), then retry the MCP call.

  ConnectorNo auth