Xata for AI agents
Xata is a serverless database platform focused on developer experience, and this connection covers organization-level settings like regions, instance types, and API keys. 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 Xata.
List available regions
Check which regions a database can be deployed to, a read-only lookup.
Get organization details
Pull the organization's current settings and limits as a read-only check.
Confirm before revoking an API key
Check with the user before revoking an organization API key, since anything using it would stop working.
8 Xata actions, graded by risk.
Every Xata action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- xata.list_imagesList Available Images
- xata.list_regionsList Available Regions
- xata.list_extensionsList Extensions
- xata.get_organizationGet Organization Details
- xata.list_org_api_keysList Organization API Keys
- xata.get_project_limitsGet project resource limits
- xata.list_instance_typesList Instance Types
write
1Create and change things. Allow, or ask the user first.
- xata.update_organizationUpdate Organization
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Xata in three steps.
- 01Your users connect XataThey add their Xata api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “update Organization” can wait for the user to approve.
- 03Any agent can actYour agent calls Xata through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('xata', { read: 'allow', write: 'ask', // update_organization destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Xata connects.
Users add their Xata 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 Xata 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 Xata from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore databases and spreadsheets apps.
Xata and Arc0, answered.
Can I use Xata with Claude, ChatGPT or Cursor?
Yes. Connect Xata 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 Xata actions you allow.
How do users connect Xata?
Users add their Xata 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 Xata actions can my agent take?
8 in total: 7 read, 1 write and 0 destructive, such as “update Organization”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Xata?
Yes. Allow read actions and deny writes in the Xata policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Xata too?
Yes. The same Xata connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Xata into your agent.
Your users connect Xata once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan