CSVBox for AI agents
CSVBox configures spreadsheet importers, letting a product accept CSV uploads from users and route the cleaned data to a chosen destination. 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 CSVBox.
Create a new spreadsheet importer
Create a new sheet importer configured to send data to a specific destination.
Submit a file import
Submit a spreadsheet file for import once a user has uploaded it.
Verify API credentials
Verify API credentials are still valid before setting up a brand new importer.
4 CSVBox actions, graded by risk.
Every CSVBox 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.
- csvbox.verify_credentialsVerify CSVBox Credentials
write
3Create and change things. Allow, or ask the user first.
- csvbox.create_sheetCreate CSVBox Sheet
- csvbox.update_sheetUpdate CSVBox Sheet
- csvbox.submit_file_importSubmit CSVBox File Import
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
CSVBox in three steps.
- 01Your users connect CSVBoxThey add their CSVBox api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create CSVBox Sheet” can wait for the user to approve.
- 03Any agent can actYour agent calls CSVBox through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('csvbox', { read: 'allow', write: 'ask', // create_sheet destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How CSVBox connects.
Users add their CSVBox 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 CSVBox 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 CSVBox from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore databases and spreadsheets apps.
CSVBox and Arc0, answered.
Can I use CSVBox with Claude, ChatGPT or Cursor?
Yes. Connect CSVBox 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 CSVBox actions you allow.
How do users connect CSVBox?
Users add their CSVBox 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 CSVBox actions can my agent take?
4 in total: 1 read, 3 write and 0 destructive, such as “create CSVBox Sheet”. Your policies decide which of them each agent may call.
Can I make my agent read-only in CSVBox?
Yes. Allow read actions and deny writes in the CSVBox policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call CSVBox too?
Yes. The same CSVBox connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug CSVBox into your agent.
Your users connect CSVBox once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan