# Uploadcare MCP > Uploadcare lets you manage your entire media pipeline directly through natural language conversation. Connect it to your AI agent to list files, check technical metadata, organize collections, and execute bulk operations like deleting or storing assets without ever touching a dashboard. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** file-upload, cdn, media-processing, asset-management, cloud-infrastructure, image-optimization ## Description This MCP connects your Uploadcare account, giving your AI agent full control over your file infrastructure. Instead of logging into the web dashboard for every task—checking dimensions, verifying CDN URLs, or monitoring storage quotas—you simply ask your agent to handle it. It lets you manage assets from creation to archival. You can list all existing files and inspect their technical metadata on demand. If you need to clean house, you don't have to manually select hundreds of outdated images; you just tell the agent to batch delete them. For large-scale data projects, it also handles copying files to external storage like S3 buckets, or marking temporary assets as permanently stored when they’re ready for prime time. If your workflow involves any kind of media distribution—from product photography to massive content libraries—this MCP is the control center you need. It's available here on Vinkius so you can connect it easily from Claude, Cursor, or any other AI-compatible client. ## Tools ### batch_delete_files Permanently removes multiple selected files from the project in one action. This change cannot be undone. ### batch_store_files Designates a group of temporary files, marking them as permanently stored and active assets. ### copy_file Copies an existing file to specified local or remote storage targets like S3 buckets. ### delete_file Permanently removes a single file and all its derived variants from Uploadcare. This action is irreversible. ### get_file_details Retrieves specific technical information, like dimensions or mime type, for one asset. ### get_group_details Provides detailed information about a specific file group, including its contents and status. ### get_project_info Pulls project-level metrics, showing current storage usage and bandwidth consumption totals. ### list_files Retrieves a paginated list of all files currently stored in the Uploadcare project. ### list_file_groups Lists all immutable file collections (groups) that have been created within the project. ### store_file Marks a single temporary file, moving it to permanent storage status. ## Prompt Examples **Prompt:** ``` What is our current project storage and bandwidth usage? ``` **Response:** ``` Based on your project info, you currently have 15.2 GB stored across 45,120 active files. Your bandwidth for this billing period is at 230 GB. This places you at 85% of your current plan limits. Would you like me to inspect and list the largest files so we can batch delete some test data? ``` **Prompt:** ``` Can you check the dimensions and CDN URL for file UUID `9cd83...`? ``` **Response:** ``` I checked the asset. It's a `hero-banner.jpg` (mime_type: image/jpeg) weighing 2.4MB. It is currently marked as permanently stored. Its dimensions are 3840x2160 pixels. The raw public CDN access url is `https://ucarecdn.com/9cd83.../`. Let me know if you want me to copy this to an S3 bucket. ``` **Prompt:** ``` Batch delete these 4 outdated temporary images: `e33b...`, `f55a...`, `8c11...`, `ab99...`. ``` **Response:** ``` I've successfully executed the `batch_delete_files` command. All 4 assets (`e33b...`, `f55a...`, `8c11...`, `ab99...`) and their related CDN variants have been irrevocably deleted from your Uploadcare project. Your storage limits have been safely reduced. ``` ## Capabilities ### Inspect File Metadata Get technical details for a specific file, including its size, dimensions, and direct public CDN URL. ### Manage Collections List entire groups of files or collections, and inspect exactly which individual assets belong to them. ### Perform Bulk Operations Mark multiple temporary files as permanent storage using batch operations, or irreversibly delete large sets of outdated content at once. ### Monitor Project Usage Retrieve current project-level data on your account's total stored capacity and bandwidth consumption limits. ### Transfer Files Copy existing media files manually to external destinations like S3 buckets or local storage targets. ## Use Cases ### Auditing old content libraries The Content Manager needs to figure out how much space is taken up by temporary assets. They ask the agent, and it calls `get_project_info` to report current storage limits. Then they identify 50 unused images via `list_files` and use `batch_delete_files` to clear the quota. ### Preparing a file for external ingestion The Software Engineer needs an asset ready in another system. They ask the agent to check the file's technical metadata using `get_file_details`, confirm its CDN URL, and then use `copy_file` to send it directly to their staging S3 bucket. ### Archiving project resources The DevOps Team identifies a set of temporary images that should be kept long-term. They instruct the agent using `batch_store_files`, moving those files from volatile temporary status to permanent, reliable storage. ### Inspecting a known asset group The Product Team needs to confirm which files belong to 'Q3 Campaign Images'. They ask the agent to call `list_file_groups` to find the group name, then use `get_group_details` to verify all included assets are present. ## Benefits - You stop clicking through dashboards. Your agent handles complex tasks, such as running `get_file_details` to check a CDN URL or dimensions instantly. - Mass cleanup is effortless. Instead of manually deleting files, you use batch operations like `batch_delete_files` on outdated assets in seconds. - Always know your limits. The agent calls `get_project_info` so you can monitor storage and bandwidth usage without guessing if you're running low. - Automate transfers. Use `copy_file` to automatically move necessary media from Uploadcare into external systems like S3 buckets for backup or processing. - Organize assets logically. You can list all file groups using `list_file_groups` and then check the contents of any group with `get_group_details`. ## How It Works The bottom line is you treat your entire media infrastructure like a conversation; you don't interact with confusing dashboards. 1. Subscribe to this MCP and provide your Uploadcare Public and Secret Keys. 2. Connect the credentials to your preferred AI client (Claude, Cursor, etc.). 3. Use natural language prompts to instruct your agent to perform file actions or retrieve data. ## Frequently Asked Questions **Can the Uploadcare MCP help me find file metadata?** Yes, it can. You use `get_file_details` to retrieve technical metadata for any specific asset, including its dimensions and CDN URL. **How do I delete a lot of old images with Uploadcare MCP?** You run the `batch_delete_files` tool. This permanently removes multiple assets in one operation, which is much faster than deleting them individually. **Does this MCP monitor my storage quota?** Yes. The agent calls `get_project_info` to provide real-time metrics on your total account storage and bandwidth usage limits. **What is the difference between listing files and listing groups with Uploadcare MCP?** Using `list_files` shows every individual asset in your project. However, you use `list_file_groups` to see immutable collections, which organize those assets logically. **Can I move files out of Uploadcare using the MCP?** Yes. The agent uses the `copy_file` tool to copy existing media directly to external storage targets like S3 buckets.