Uploadcare

@Uploadcare list all image files uploaded in the last 7 days, sorted by size descending

Found 23 image files uploaded in the past week. The largest is a 4.2MB PNG (product-hero-v3.png) uploaded 2 days ago, followed by a 3.8MB JPEG (team-photo-final.jpg) from 5 days ago. The smallest is a 180KB thumbnail. All files are stored and ready for delivery via CDN. Total storage used by these files: 42.1MB.

This example shows the MCP's file-listing capability with time and type filters. The actual response includes file UUIDs, CDN URLs, and MIME types. Note that pagination kicks in after 100 results—large libraries require multiple calls or adjusted limits.

@Uploadcare create a webhook that notifies https://api.myapp.com/media-ready when any file upload completes

Webhook created successfully. ID: wh_a7f3e9d2. Now listening for 'file.uploaded' events in your project and will POST to https://api.myapp.com/media-ready with file metadata (UUID, URL, size, MIME type) whenever an upload finishes. The webhook is active immediately and includes a signing secret for verifying payloads.

This demonstrates the MCP's ability to wire Uploadcare events into your own services. You'll need your project UUID before calling this tool. Be aware that webhook creation is a side-effect—deleting the webhook later requires its ID, which you should store.

@Uploadcare get the download URL and metadata for file abc123-def456-ghi789, then summarize its usage stats and suggest if we should archive it

File abc123-def456-ghi789 is a 1.8MB PDF named 'Q4-report-draft.pdf', uploaded 6 months ago. Download URL (valid for 24 hours): https://ucarecdn.com/abc123.../Q4-report-draft.pdf. Metadata shows 3 downloads in the first week, none since. Given the low access frequency and age, this file is a candidate for archival or deletion if your retention policy allows—it's consuming storage with minimal active use.

This example pairs the MCP's file-info retrieval with the AI's reasoning to surface actionable insights. The download URL expires, so it's best for immediate use. Metadata keys vary by what you've stored—this MCP can read and delete custom keys but not create them.

When Uploadcare wins for support ticket attachments

A 6-person support team handling 200 tickets a week needs to track which customer files are still referenced in open cases and which can be purged. Uploadcare's metadata tools let you tag files with ticket IDs at upload, then use List Uploadcare Files with filters to audit what's still active. The Get File Info tool pulls usage stats so you know if a file is actually being served or just sitting in storage. This works well up to about 10,000 files per month—beyond that, you'll want a dedicated DAM with better search. If your team already routes attachments through Zendesk or Intercom, those native integrations are simpler. But if you're building a custom support portal or need to manage files outside the ticketing system, Uploadcare gives you the metadata hooks without writing your own storage layer.

When webhooks make sense for creative handoffs

A 3-person marketing team at a B2B SaaS company uploads campaign images to a shared folder, and the designer needs to know the moment a file is approved so they can push it to the CMS. Uploadcare's Create Webhook tool lets you subscribe to file events—upload, metadata change, deletion—and ping a Slack channel or trigger a Zapier flow when the status flips to approved. The Delete Webhook tool cleans up old subscriptions when campaigns end. This setup shines when you have 5-15 active campaigns at once and need real-time handoffs without checking a folder manually. If your team is smaller or only runs one campaign at a time, a shared Google Drive with notifications is easier. If you're managing hundreds of assets with complex approval chains, you need a full DAM like Bynder. Uploadcare sits in the middle: enough automation to skip manual checks, not so much overhead that setup takes longer than the campaign.

When file metadata scales for UGC at early stage

A 4-person startup building a community platform needs to let users upload profile photos and post images, then moderate them before they go live. Uploadcare's Set File Metadata and Delete File Metadata Key tools let you tag uploads with moderation status, reviewer ID, and approval timestamps without building your own database schema. The List Files tool with filters pulls the moderation queue each morning, and Get File Info confirms the file is still accessible before you approve it. This works cleanly up to about 5,000 uploads a month—enough for an early-stage product with a few hundred active users. Once you hit 20,000 uploads a month or need automated moderation with ML, you'll outgrow this and need Cloudinary or a custom pipeline. But for the first year of a UGC product, Uploadcare's metadata layer is faster than rolling your own storage and cheaper than enterprise CDN pricing.