4,500+ servers built on MCP Fusion
Vinkius

Uploadcare MCP. Manage media assets, from metadata checks to bulk deletion.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Uploadcare MCP on Cursor AI Code Editor MCP Client Uploadcare MCP on Claude Desktop App MCP Integration Uploadcare MCP on OpenAI Agents SDK MCP Compatible Uploadcare MCP on Visual Studio Code MCP Extension Client Uploadcare MCP on GitHub Copilot AI Agent MCP Integration Uploadcare MCP on Google Gemini AI MCP Integration Uploadcare MCP on Lovable AI Development MCP Client Uploadcare MCP on Mistral AI Agents MCP Compatible Uploadcare MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Uploadcare lets you manage your entire media infrastructure—uploading, retrieving metadata, organizing, and deleting files—directly through your AI agent. You control file storage, monitor bandwidth usage via `get_project_info`, and run massive cleanup operations using tools like `batch_delete_files`.

It's complete asset lifecycle management without opening a dashboard.

What your AI agents can do

Batch delete files

Irrevocably and permanently deletes multiple specified files in a single operation.

Batch store files

Marks several temporary assets as permanent storage, ensuring they survive standard cleanup cycles.

Copy file

Copies a specific file to either local or remote cloud storage targets (e.g., S3).

+ 7 more capabilities included
Retrieve asset technical metadata

The agent fetches dimensions, MIME types, and raw CDN URLs for a specific file ID using get_file_details.

Monitor project usage stats

You get real-time data on current storage consumption (GB) and remaining bandwidth quota via get_project_info.

Perform batch file deletions

The agent irrevocably removes multiple specified files and all their CDN variants using the batch_delete_files tool.

Copy assets to external storage

You direct the AI client to copy an existing file either locally or to a remote cloud target like S3, controlled by copy_file.

List and inspect file groups

The agent lists immutable collections of assets (list_file_groups) and then details the specific files contained within them using get_group_details.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Uploadcare MCP Server: 10 Tools for File Management

Use these tools to list files, check metadata, copy assets, or perform irreversible batch deletions across your entire media infrastructure.

batch019d7619

batch delete files

Irrevocably and permanently deletes multiple specified files in a single operation.

batch019d7619

batch store files

Marks several temporary assets as permanent storage, ensuring they survive standard cleanup cycles.

copy019d7619

copy file

Copies a specific file to either local or remote cloud storage targets (e.g., S3).

delete019d7619

delete file

Irrevocably removes one specific file and all its derived CDN variants from the project.

get019d7619

get file details

Retrieves technical metadata, including dimensions and raw CDN URLs, for a single file ID.

get019d7619

get group details

Pulls detailed information about a specific immutable file collection or group.

get019d7619

get project info

Retrieves current project metadata, showing total storage used and bandwidth consumption statistics.

list019d7619

list file groups

Lists all the immutable file collections (groups) available in your Uploadcare project.

list019d7619

list files

Lists all files stored in the project, supporting pagination via a limit parameter.

store019d7619

store file

Marks a single temporary file as permanently stored within your account.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Uploadcare, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

You manage your whole media stack—uploading, checking metadata, grouping assets, cleaning house—straight through your AI client. You don't have to touch a dashboard; you just tell your agent what to do.

Getting the Raw Data:

To figure out what files you’ve got and how big they are, start with list_files. This tool gives you an inventory of every asset stored in the project and lets you paginate through massive lists using a limit parameter. For specific info on one file ID, run get_file_details; that pulls technical metadata like dimensions, MIME types, and all the raw CDN URLs associated with it.

Need to know about whole collections? You can use list_file_groups first to see every immutable group available in your project, then dive deeper into those specific files using get_group_details.

Handling Assets: Storing and Deleting:

When you’re done with a temporary file or need to promote it to permanent storage, you've got two options. For single assets, use store_file to mark that one temp item as permanent within your account. If you've got a bunch of temps waiting to be solidified, run batch_store_files to mark multiple temporary assets for permanent survival past any standard cleanup cycles.

Conversely, when you need to wipe something out, the tools are brutal about it because they should be. To permanently delete one specific file and all its derived CDN variants, use delete_file. If you’re doing a massive purge of several files at once, don't sweat it; batch_delete_files irrevocably removes multiple specified files and every single variant generated from them in one go.

Moving and Copying Assets:

You can move assets where you need 'em. You tell your agent to use copy_file, which copies an existing file either to a local destination or to a remote cloud target, like S3. This lets you duplicate files across different storage systems without re-uploading.

Monitoring Your Usage:

You gotta keep tabs on your bills and your quota. Run get_project_info when you want real-time data showing how much total storage you've used (in GB) and what your remaining bandwidth consumption stats are. That’s your quick check to see if you're running low or burning through capacity.

The Workflow:

Your agent can handle the whole lifecycle: you list files with list_files, grab technical specs on a specific ID using get_file_details and group contents via get_group_details. If those assets are good, you might use copy_file to send them offsite. Once they're safe, you can either permanently mark 'em using batch_store_files, or if they’ve served their purpose, wipe the slate clean using batch_delete_files for a complete removal of all associated data.

How Uploadcare MCP Works

  1. 1 Subscribe to this server and provide your Uploadcare Public and Secret Keys.
  2. 2 Connect your AI client (Claude, Cursor, etc.) and prompt it with an action (e.g., 'What is our bandwidth usage?').
  3. 3 The agent invokes the necessary tool (get_project_info) and returns structured data detailing your asset inventory or status.

The bottom line is: you tell your AI client what you need done, it runs the Uploadcare API call, and then reports the results back to you in plain language.

Who Is Uploadcare MCP For?

Anyone whose job involves managing media assets at scale. This isn't for hobbyists; this is for the DevOps engineer who needs to audit storage quotas before a deployment, or the Content Manager struggling with thousands of outdated test images that are eating up bandwidth.

DevOps Engineer

Monitors project limits using get_project_info and automates file archival by running copy_file to external S3 buckets.

Software Engineer

Debugs CDN URLs or asset metadata for a specific UUID without having to open the Uploadcare dashboard; runs get_file_details instead.

Content Manager

Cleans up massive batches of unused assets by running batch_delete_files on old temporary images, freeing storage quotas instantly.

What Changes When You Connect

  • Instantly audit storage and bandwidth quotas. Instead of guessing or manually checking a dashboard, run get_project_info to see your exact consumption metrics right now.
  • Clean up massive archives in seconds. Use batch_delete_files to wipe out thousands of outdated test images across the project—a job that used to take hours of manual clicking.
  • Maintain asset integrity when moving data. The copy_file tool lets you move assets directly from Uploadcare into external systems like S3 without needing a separate CLI script.
  • Never lose track of related content again. List all organized collections with list_file_groups, then deep-dive into the contents using get_group_details to ensure nothing is missed.
  • Get instant debugging info on any asset. Need a CDN URL or dimensions? Run get_file_details and get it back, so you can keep coding without context switching.

Real-World Use Cases

01

The Quarterly Asset Audit

A Content Manager needs to clear out all temporary assets older than six months. Instead of filtering through the dashboard by date and manually deleting in batches, they simply ask their agent: 'Batch delete all files marked as temp.' The agent runs batch_delete_files, reducing storage quotas instantly.

02

S3 Archival Workflow

A DevOps Engineer needs to migrate 50 key assets from Uploadcare into an external S3 archive. They instruct the agent to run copy_file for a list of UUIDs, confirming that every asset is securely duplicated outside of the primary CDN.

03

Debugging a Missing URL

A Software Engineer encounters an error saying a file's dimensions are wrong. Instead of opening the web console, they ask the agent to run get_file_details on the UUID and get the exact pixel count and raw CDN URL in their chat window.

04

Checking Storage Overages

A Product Team lead wants to know if recent user uploads are pushing them over budget. They run get_project_info, which immediately reports the current GB stored and the remaining bandwidth quota, allowing for immediate resource planning.

The Tradeoffs

Listing files when you know the UUID

Trying to run list_files just to confirm if a single file exists. This is slow and returns hundreds of irrelevant results.

If you have the specific asset ID, always use get_file_details. It gives you immediate confirmation on that one file without listing the entire project inventory.

Deleting assets piecemeal

Running delete_file ten times for ten slightly outdated images. This is slow, tedious, and error-prone.

If you have a list of many files to remove, use batch_delete_files. It handles the entire group in one single, powerful operation.

Ignoring temporary status

A developer uploads assets and forgets they need to mark them as permanent later. The data might get deleted during routine cleanup.

If an asset needs to survive standard temp file cycles, use store_file or batch_store_files. This makes it a permanent part of your infrastructure.

When It Fits, When It Doesn't

Use this server if your core workflow involves managing the infrastructure and lifecycle of assets—meaning you need to monitor quotas, perform large-scale cleanup, or move data between systems. If you only need simple file transfers that don't involve metadata (e.g., just moving a ZIP archive), a generic cloud SDK might suffice. Don't use this if your primary task is content creation; you need the assets first. Also, remember: running batch_delete_files is irreversible, so always confirm the UUID list before executing.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Uploadcare. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

batch_delete_files batch_store_files copy_file delete_file get_file_details get_group_details get_project_info list_file_groups list_files store_file

Checking file metadata and project usage shouldn't require navigating five different dashboards.

Right now, checking your CDN URLs or figuring out if you’re running low on bandwidth means opening the Uploadcare dashboard. You click to 'Usage,' then switch tabs to 'Assets,' then maybe open a secondary panel just for metadata. It's slow, and it forces you into context switching.

With this MCP server, you simply ask your agent: 'What are our current storage limits?' or 'Give me the CDN URL for UUID X.' You get structured data back in chat instantly. Zero clicks required.

Uploadcare MCP Server: Control asset movement and bulk deletion.

When you need to archive old assets, the manual process involves identifying groups of IDs, writing a script, and then executing the delete command. It's complex, brittle, and time-consuming.

Now, tell your agent: 'Run `batch_delete_files` on all test images in this group.' The job runs instantly. You manage infrastructure cleanup using plain language commands.

Common Questions About Uploadcare MCP

Can I check the dimensions and CDN URL with get_file_details? +

Yes, get_file_details retrieves technical metadata for a single file. You'll get details like MIME type, size in MB, and the raw public CDN access URL.

How do I monitor my storage usage with get_project_info? +

get_project_info delivers real-time metrics. It tells you exactly how many GB are stored across your project and what bandwidth quota remains for the billing period.

What is the difference between delete_file and batch_delete_files? +

delete_file removes one specific asset ID. batch_delete_files is used when you have multiple assets (UUIDs) that need to be removed simultaneously.

Can I move files to S3 using the copy_file tool? +

Yes, copy_file copies existing files. It supports target endpoints like local storage or remote cloud buckets, letting you archive data outside of Uploadcare.

How do I list all my file collections using list_file_groups? +

It lists every immutable collection (group) in your project. You can then use get_group_details to see exactly which individual files are contained within any specific group.

When I use list_files, how do I handle projects with thousands of assets? +

The tool supports pagination via a limit parameter. You'll need to make multiple calls or loop the function, adjusting the offset and increasing the limit until it returns an empty set.

What is the difference between store_file and batch_store_files? +

Both tools mark files as permanent. Use store_file for a single file, but use batch_store_files when you need to change the status of multiple temporary assets at once.

If I run delete_file on an asset, does it remove all its CDN variants? +

Yes. Deleting a source file permanently removes that file and every variant associated with it from your Uploadcare project.

Can my AI agent batch delete unused Uploadcare files? +

Yes! Provide your agent with the list of unused UUIDs or ask it to identify temporary incomplete uploads, and simply command it to batch delete these assets. The agent uses the batch_delete_files tool to permanently erase them from the CDN instantly, freeing up your project's storage.

How can I quickly check my current CDN bandwidth and storage usage? +

Instead of digging through the web dashboard, ask your AI agent to get project info. It instantly fetches your Uploadcare project-level metadata, returning your precise storage usage (bytes), traffic bandwidth usage, and active file count. Perfect for quick billing audits.

Will my temporary UI uploads expire automatically? +

By default, temporary files uploaded via your front-end will be wiped after 24 hours. To prevent this, you can ask your agent to store this file or batch store a bunch of UUIDs. The agent communicates with Uploadcare to mark the files as permanently stored, saving them from the garbage collector.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Uploadcare. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.