TiDB Cloud for AI agents
TiDB Cloud is a managed database platform, and this connection covers control-plane resources like clusters, branches, and billing rather than the data inside them. 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 TiDB Cloud.
List clusters in the organization
Pull the current list of TiDB clusters as a read-only inventory check.
Check the monthly bill
Read the current month's billing total before it's reported to finance.
Review audit logs before a change
Read recent audit log entries to see who touched a cluster before making further changes.
10 TiDB Cloud actions, graded by risk.
Every TiDB Cloud action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- tidb_cloud.get_clusterGet Cluster
- tidb_cloud.list_regionsList Regions
- tidb_cloud.list_branchesList Branches
- tidb_cloud.list_clustersList Clusters
- tidb_cloud.list_data_appsList Data Apps
- tidb_cloud.list_audit_logsList Audit Logs
- tidb_cloud.get_monthly_billGet Monthly Bill
- tidb_cloud.list_import_tasksList Import Tasks
- tidb_cloud.list_data_app_deploymentsList Data App Deployments
- tidb_cloud.list_organization_membersList Organization Members
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
TiDB Cloud in three steps.
- 01Your users connect TiDB CloudThey add their TiDB Cloud api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls TiDB Cloud through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('tidb_cloud', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How TiDB Cloud connects.
Users add their TiDB Cloud 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 TiDB Cloud 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 TiDB Cloud from any agent.
More databases and spreadsheets apps.
TiDB Cloud and Arc0, answered.
Can I use TiDB Cloud with Claude, ChatGPT or Cursor?
Yes. Connect TiDB Cloud 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 TiDB Cloud actions you allow.
How do users connect TiDB Cloud?
Users add their TiDB Cloud 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 TiDB Cloud actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in TiDB Cloud?
Yes. Allow read actions and deny writes in the TiDB Cloud policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call TiDB Cloud too?
Yes. The same TiDB Cloud connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug TiDB Cloud into your agent.
Your users connect TiDB Cloud once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan