ImgBB MCP integration for AI agents.
Connect AI agents to ImgBB through 1 structured actions, including upload image. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- 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 ImgBB integration exposes
The ImgBB Agent App exposes 1 provider-backed actions for design & media and storage work. Its current contract lets an authorized agent upload one image to imgbb from a public url or base64 content and return the hosted image metadata. 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 ImgBB account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ImgBB capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
upload_imageWRITEUpload one image to ImgBB from a public URL or Base64 content and return the hosted image metadata.
INPUTS: imageUrl / contentBase64 / name / expiration
INPUT CONTRACTS
Know what the action needs before it runs.
upload_image
imageUrlOPTIONAL- The public image URL to upload to ImgBB.
contentBase64OPTIONAL- The Base64-encoded image bytes to upload to ImgBB.
nameOPTIONAL- The optional file name to associate with the upload.
expirationOPTIONAL- The number of seconds after which ImgBB should automatically delete the upload.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Upload Image
Upload one image to ImgBB from a public URL or Base64 content and return the hosted image metadata. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
upload_imageControl Upload Image
Upload one image to ImgBB from a public URL or Base64 content and return the hosted image metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
upload_imageVerify with Upload Image
Upload one image to ImgBB from a public URL or Base64 content and return the hosted image metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
upload_imageSAFETY BOUNDARY
Operate ImgBB with explicit limits
- Authorize ImgBB 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 ImgBB rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ImgBB task completed successfully.
CONNECTION MODEL
API key
ImgBB API key sent as the key query parameter on the upload endpoint. Get or view it on the official API page: https://api.imgbb.com/.
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
- 0
- WRITE SIGNALS
- 1
- 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 ImgBB.