ImgBB for AI agents
ImgBB is a free image hosting service for uploading and sharing images with a public link. Creative teams use it to generate this kind of asset on demand instead of by hand. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in ImgBB.
Upload an image for sharing
Upload an image to get a shareable link to drop into a document or chat message.
Check API key details
Check the account's API key details before scripting a batch upload.
Confirm upload before sharing
Confirm an uploaded image renders correctly before sending the link to a client.
2 ImgBB actions, graded by risk.
Every ImgBB action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- imgbb.get_api_keyGet ImgBB API Key
write
1Create and change things. Allow, or ask the user first.
- imgbb.upload_imageUpload Image to ImgBB
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
ImgBB in three steps.
- 01Your users connect ImgBBThey add their ImgBB api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “upload Image to ImgBB” can wait for the user to approve.
- 03Any agent can actYour agent calls ImgBB through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('imgbb', { read: 'allow', write: 'ask', // upload_image destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How ImgBB connects.
Users add their ImgBB api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same ImgBB connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use ImgBB from any agent.
ImgBB and Arc0, answered.
Can I use ImgBB with Claude, ChatGPT or Cursor?
Yes. Connect ImgBB to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the ImgBB actions you allow.
How do users connect ImgBB?
Users add their ImgBB api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which ImgBB actions can my agent take?
2 in total: 1 read, 1 write and 0 destructive, such as “upload Image to ImgBB”. Your policies decide which of them each agent may call.
Can I make my agent read-only in ImgBB?
Yes. Allow read actions and deny writes in the ImgBB policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call ImgBB too?
Yes. The same ImgBB connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug ImgBB into your agent.
Your users connect ImgBB once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan