Drop to CDN for AI agents
Drop to CDN uploads files and publishes HTML pages to public CDN URLs, then lets users list, inspect, and remove hosted files. 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 Drop to CDN.
Publish a page to a public URL
Publish an HTML page to a CDN URL so it can be shared with someone outside the team.
Check hosted file usage
Get account usage to see how much storage and bandwidth hosted files are consuming.
Confirm before permanently deleting a file
Require approval before permanently deleting a hosted file, since the action cannot be undone.
6 Drop to CDN actions, graded by risk.
Every Drop to CDN action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- drop_to_cdn.get_fileGet File
- drop_to_cdn.list_filesList Files
- drop_to_cdn.get_account_usageGet Account Usage
write
2Create and change things. Allow, or ask the user first.
- drop_to_cdn.upload_fileUpload File
- drop_to_cdn.publish_pagePublish Page
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- drop_to_cdn.delete_filePermanently Delete File
Drop to CDN in three steps.
- 01Your users connect Drop to CDNThey add their Drop to CDN api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “upload File” can wait for the user, and “permanently Delete File” can be denied outright.
- 03Any agent can actYour agent calls Drop to CDN through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('drop_to_cdn', { read: 'allow', write: 'ask', // upload_file destructive: 'deny', // delete_file }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Drop to CDN connects.
Users add their Drop to CDN 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 Drop to CDN 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 Drop to CDN from any agent.
Drop to CDN and Arc0, answered.
Can I use Drop to CDN with Claude, ChatGPT or Cursor?
Yes. Connect Drop to CDN 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 Drop to CDN actions you allow.
How do users connect Drop to CDN?
Users add their Drop to CDN 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 Drop to CDN actions can my agent take?
6 in total: 3 read, 2 write and 1 destructive, such as “upload File”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Drop to CDN?
Yes. Actions like “permanently Delete File” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Drop to CDN too?
Yes. The same Drop to CDN connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Drop to CDN into your agent.
Your users connect Drop to CDN once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan