Files.com for AI agents
Files.com is a secure cloud storage and file transfer platform for storing, sharing, and managing files across cloud and on-premises systems. 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 Files.com.
Check folder contents
List the contents of a folder to confirm a file has arrived before notifying a team member.
Review sharing permissions
List permissions on a folder to check who has access before granting a new share.
Confirm before deleting a share
Require approval before deleting a share, since it revokes access for everyone using that link.
7 Files.com actions, graded by risk.
Every Files.com action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- files_com.list_groupsList Groups
- files_com.list_foldersList Folders
- files_com.list_permissionsList Permissions
- files_com.get_s3_key_for_uploadGet S3 Key for Upload
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
3Delete, cancel or archive. Ask first, or deny outright.
- files_com.delete_shareDelete Share
- files_com.delete_api_keyDelete API Key
- files_com.delete_permissionDelete Permission
Files.com in three steps.
- 01Your users connect Files.comThey add their Files.com api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “updates” can wait for the user, and “delete Share” can be denied outright.
- 03Any agent can actYour agent calls Files.com through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('files_com', { read: 'allow', write: 'ask', destructive: 'deny', // delete_share }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Files.com connects.
Users add their Files.com 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 Files.com 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 Files.com from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Files.com and Arc0, answered.
Can I use Files.com with Claude, ChatGPT or Cursor?
Yes. Connect Files.com 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 Files.com actions you allow.
How do users connect Files.com?
Users add their Files.com 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 Files.com actions can my agent take?
7 in total: 4 read, 0 write and 3 destructive. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Files.com?
Yes. Actions like “delete Share” 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 Files.com too?
Yes. The same Files.com connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Files.com into your agent.
Your users connect Files.com once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan