Uploadcare MCP integration for AI agents.
Connect AI agents to Uploadcare through 7 structured actions, including get file info, delete file, and store file. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Uploadcare integration exposes
The Uploadcare Agent App exposes 7 provider-backed actions for storage and design & media work. Its current contract lets an authorized agent get uploadcare file metadata by uuid, remove an uploadcare file from storage by uuid, and mark an uploadcare file as permanently stored. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Uploadcare account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Uploadcare capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_file_infoREADGet Uploadcare file metadata by UUID.
INPUTS: uuid / include
delete_fileHIGH IMPACTRemove an Uploadcare file from storage by UUID.
INPUTS: uuid
store_fileREVIEWMark an Uploadcare file as permanently stored.
INPUTS: uuid
get_group_infoREADGet an Uploadcare file group by its group ID.
INPUTS: uuid
get_project_infoREADGet Uploadcare project details for the connected public key.
list_filesREADList Uploadcare files with documented pagination and filters.
INPUTS: removed / stored / limit / ordering / from
list_groupsREADList Uploadcare file groups with documented pagination.
INPUTS: limit / from / ordering
INPUT CONTRACTS
Know what the action needs before it runs.
get_file_info
uuidREQUIRED- The Uploadcare file UUID.
includeOPTIONAL- Additional Uploadcare fields to include, such as appdata.
delete_file
uuidREQUIRED- The Uploadcare file UUID.
store_file
uuidREQUIRED- The Uploadcare file UUID.
get_group_info
uuidREQUIRED- The Uploadcare group ID, for example a UUID followed by ~ and size.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get File Info
Get Uploadcare file metadata by UUID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_file_infoControl Delete File
Remove an Uploadcare file from storage by UUID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
delete_fileVerify with Get Group Info
Get an Uploadcare file group by its group ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_group_infoSAFETY BOUNDARY
Operate Uploadcare with explicit limits
- Authorize Uploadcare with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_file` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Uploadcare rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Uploadcare task completed successfully.
CONNECTION MODEL
API key
Uploadcare Secret API Key used to sign REST API requests. Create or view API keys in the Uploadcare dashboard: https://app.uploadcare.com/projects/-/api-keys/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Uploadcare.