Imgix MCP integration for AI agents.
Connect AI agents to Imgix through 4 structured actions, including get source, update source, and purge asset. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 4
- 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 Imgix integration exposes
The Imgix Agent App exposes 4 provider-backed actions for design & media and developer tools work. Its current contract lets an authorized agent retrieve a single imgix source by its id, update an imgix source by sending json:api source attributes to the management api, and purge an imgix asset url from cache so subsequent requests fetch a fresh origin copy. 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 Imgix account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Imgix capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_sourceREADRetrieve a single Imgix Source by its ID.
INPUTS: sourceId / fieldsSources
update_sourceWRITEUpdate an Imgix Source by sending JSON:API Source attributes to the Management API.
INPUTS: sourceId / attributes
purge_assetREVIEWPurge an Imgix asset URL from cache so subsequent requests fetch a fresh origin copy.
INPUTS: url / sourceId / subImage
list_sourcesREADList Imgix Sources with optional pagination, sorting, sparse fields, and source filters.
INPUTS: sort / pageSize / pageNumber / fieldsSources / filterName
INPUT CONTRACTS
Know what the action needs before it runs.
get_source
sourceIdREQUIRED- The unique Imgix Source identifier.
fieldsSourcesOPTIONAL- Comma-separated Source fields to return through the fields[sources] sparse fieldset.
update_source
sourceIdOPTIONAL- The unique Imgix Source identifier.
attributesOPTIONAL- Source attributes to send to Imgix. Use the official Imgix Source attribute keys for the selected source type.
purge_asset
urlREQUIRED- The full Imgix asset URL to purge.
sourceIdOPTIONAL- Optional Imgix Source ID used to scope the purge.
subImageOPTIONAL- Whether to purge only sub-images or variants of the asset.
list_sources
sortOPTIONAL- Comma-separated sort fields accepted by Imgix, such as -date_deployed,name.
pageSizeOPTIONAL- Number of Sources to return per page.
pageNumberOPTIONAL- Zero-indexed page number to fetch.
fieldsSourcesOPTIONAL- Comma-separated Source fields to return through the fields[sources] sparse fieldset.
filterNameOPTIONAL- Filter Sources by name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Source
Retrieve a single Imgix Source by its ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_sourceControl Update Source
Update an Imgix Source by sending JSON:API Source attributes to the Management API. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
update_sourceVerify with List Sources
List Imgix Sources with optional pagination, sorting, sparse fields, and source filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_sourcesSAFETY BOUNDARY
Operate Imgix with explicit limits
- Authorize Imgix 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.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Imgix rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Imgix task completed successfully.
CONNECTION MODEL
API key
Imgix Management API key sent as a Bearer token. Create or copy an API key from the Imgix dashboard API keys page: https://dashboard.imgix.com/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
- 2
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- 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 Imgix.