Cincopa MCP integration for AI agents.
Connect AI agents to Cincopa through 4 structured actions, including list asset tags, list assets, and list galleries. Review authentication, inputs, workflo…
- 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 Cincopa integration exposes
The Cincopa Agent App exposes 4 provider-backed actions for design & media and storage work. Its current contract lets an authorized agent list the asset tag cloud available in a cincopa account, list assets from a cincopa account with optional metadata filters, and list galleries from a cincopa account with optional search and tag filters. 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 Cincopa account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cincopa capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_asset_tagsREADList the asset tag cloud available in a Cincopa account.
list_assetsREADList assets from a Cincopa account with optional metadata filters.
INPUTS: search / types / rid / referenceId / tag
list_galleriesREADList galleries from a Cincopa account with optional search and tag filters.
INPUTS: search / page / itemsPerPage / filterTags
list_gallery_itemsREADList items from one Cincopa gallery by FID.
INPUTS: fid / details / page / itemsPerPage
INPUT CONTRACTS
Know what the action needs before it runs.
list_assets
searchOPTIONAL- Free-text search term for asset metadata.
typesOPTIONAL- Asset types to include, such as image, video, audio, or other.
ridOPTIONAL- Exact Cincopa RID to search for.
referenceIdOPTIONAL- Exact Cincopa reference_id to search for.
tagOPTIONAL- Asset tag filter value.
list_galleries
searchOPTIONAL- Search term matched against gallery captions, descriptions, IDs, and tags.
pageOPTIONAL- Result page number to request from Cincopa.
itemsPerPageOPTIONAL- Maximum number of galleries to request in one page.
filterTagsOPTIONAL- Gallery tags to include or exclude. Prefix a value with '-' to exclude it.
list_gallery_items
fidREQUIRED- The Cincopa gallery FID to inspect.
detailsOPTIONAL- Metadata field names to request from Cincopa for each gallery item.
pageOPTIONAL- Result page number to request from Cincopa.
itemsPerPageOPTIONAL- Maximum number of gallery items to request in one page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Asset Tags
List the asset tag cloud available in a Cincopa account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_asset_tagsVerify with List Assets
List assets from a Cincopa account with optional metadata filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_assetsSAFETY BOUNDARY
Operate Cincopa with explicit limits
- Authorize Cincopa with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Cincopa data may still be sensitive and should be minimized before it enters model context.
- 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 Cincopa rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cincopa task completed successfully.
CONNECTION MODEL
API key
Cincopa API token sent as the api_token query parameter.
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
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Cincopa.