ImageKit MCP integration for AI agents.
Connect AI agents to ImageKit through 7 structured actions, including get file details, delete file, and purge cache. Review authentication, inputs, workflow…
- 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 ImageKit integration exposes
The ImageKit Agent App exposes 7 provider-backed actions for design & media and storage work. Its current contract lets an authorized agent get details for the current version of an imagekit file, delete one imagekit file and all of its versions permanently, and submit a cache purge request for an imagekit file url. 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 ImageKit account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ImageKit 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_detailsREADGet details for the current version of an ImageKit file.
INPUTS: fileId
delete_fileHIGH IMPACTDelete one ImageKit file and all of its versions permanently.
INPUTS: fileId
purge_cacheREVIEWSubmit a cache purge request for an ImageKit file URL.
INPUTS: url
get_purge_statusREADGet the status of an ImageKit cache purge request.
INPUTS: requestId
get_remote_file_metadataREADGet image or video metadata from a remote URL through ImageKit.
INPUTS: url
get_uploaded_file_metadataREADGet image or video metadata for an uploaded ImageKit file.
INPUTS: fileId
list_assetsREADList or search assets in the ImageKit media library.
INPUTS: path / searchQuery / fileType / sort / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_file_details
fileIdREQUIRED- The unique ImageKit fileId returned by upload or list assets APIs.
delete_file
fileIdREQUIRED- The unique ImageKit fileId returned by upload or list assets APIs.
purge_cache
urlREQUIRED- The full ImageKit file URL to purge from cache.
get_purge_status
requestIdREQUIRED- The ImageKit purge request identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get File Details
Get details for the current version of an ImageKit file. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_file_detailsControl Delete File
Delete one ImageKit file and all of its versions permanently. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
delete_fileVerify with Get Purge Status
Get the status of an ImageKit cache purge request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_purge_statusSAFETY BOUNDARY
Operate ImageKit with explicit limits
- Authorize ImageKit 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 ImageKit rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ImageKit task completed successfully.
CONNECTION MODEL
API key
ImageKit private API key used as the HTTP Basic auth username. View or reveal it in the ImageKit dashboard under Developer options > 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 ImageKit.