Can an AI agent use TiDB Cloud?

TiDB Cloud is a hosted MySQL-compatible database with vector search and file storage for agents.

tidbcloud.comDatabases

Driven 4 Nov 2026

Evidence sha256 45b7ce0bJSONMarkdownFeedCite

L3

Does the work

  1. L0
  2. L1
  3. L2
  4. L3
  5. L4
  6. L5

Rank among the 246 products we drove

Holds up
tied #9
94/ 100
Reliability under errors
Core work done
tied #1
100%
8 of 8 core tasks
Time to get in
tied #66
6minutes
Getting in on its own
Steps on its own
tied #35
3/ 5
Find to Leave, no person

Yes. Our agent signed up for TiDB Cloud on its own in a browser with an email and password, got an API key and used its API, MCP server and CLI.

The record

Level confirmed

Not yet

Level from one drive; a second must agree.

Got in by
Sign-up in a browser6 minutes
Got as far as
Pay: reaches the checkoutA card form

Connects by

MCP, API, CLI

Agent payments

None found

  1. Find

    On its own

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

  2. Get in

    On its own · 6 minutes

    Sign-up in a browser.

  3. Use

    On its own · 8 of 8 core tasks

    Did: create, branch and delete database instances through the API or the command line; create tables, write rows and run SQL and vector-similarity searches.

  4. PayFirst stop

    Partly

    Reaches the checkout. A card form.

  5. Leave

    Partly

    Nothing to cancel. It deletes its data, but the login stays.

  • On its own
  • Partly

To reach L4: Delete its account, so its keys and login stop working.

Checked 18 Nov 2026: MCP server asks for a sign-in, OpenAPI unchanged since the check before.

Find

How an agent connects

MCP, API, OpenAPI, CLI and llms.txt found.

  • MCP server

    All tested

    Official server. Local pytidb TiDB MCP Server (stdio, 7 tools when driven, needs mcp<2 pin). Sign‑in needed to see its tools.

    mcp.tidbcloud.com/mcp

    7 tools mapped in our drive

  • API

    88 of 130 tested

    REST v1beta1 Serverless (Swagger 2.0), IAM, billing; HTTP Digest auth.

    130 operations mapped in our drive

  • OpenAPI

    Yes

    A machine-readable description of the API.

  • CLI

    112 of 132 tested

    ticloud (OAuth device login or API keys) and ti (db, fs, fs-journal, fs-vault, fs-git).

    132 commands mapped in our drive

  • SDK

    None found
  • llms.txt

    Yes

    A file that points agents to the docs.

  • Agent payments

    None found

    Reached the card form and stopped: Pay-as-you-go (Starter beyond free quota), $0 a call. It checks out through a Stripe card form. An invisible bot check loaded at checkout. It offers Link.

  • Docs

    Not read

    The drive didn't read the docs.

Get in

Getting in

Our agent tried 2 of 3 ways in; 2 worked without a person.

The way that worked

Sign-up in a browser6 minutes

  • An inboxNeeded
  • A browserNeeded
  • A personNot needed
  • Agent on a serverAPI, MCP, CLINoStops at sign-up: it works only in a browser.
  • Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does all of the core work, then stops: deletes its data, but the login stays.
  • Signed agentKnown to CloudflareYesThe sign-up page opens.

Every way in

Every way in and what happened
Way inWhat happenedWhy
Sign-up in a browserWorked
Sign-up in a browserWorkedPart of the work done
Runs locally, no accountNot triedThe same as another way
  • CrawlersThe robots.txt on auth.tidbcloud.com asks crawlers to stay off sign-up. Nothing to fix.

Use

What an agent can do with TiDB Cloud

All 8 core tasks done, and 12 of 16 others.

Core tasks

  • done there
  • offered, not tried
Core tasks of TiDB Cloud: the result and the surfaces they went through
TaskResultThrough
Create a TiDB Cloud Starter instanceDoneAPI: done thereCLI: done there
Create a table in an instanceDoneMCP: done thereCLI: offered, not tried
Run a SQL query on an instanceDoneMCP: done thereCLI: offered, not tried
Run a vector search over stored embeddingsDoneMCP: done there
Branch an instanceDoneAPI: done thereCLI: done there
Import a data file into an instanceDoneAPI: offered, not triedCLI: done there
Delete a TiDB Cloud instanceDoneAPI: done thereCLI: done there
Create a file system and write files to itDoneCLI: done there
Create a Lake warehouse and run an analytics queryPaid plan, not countedMCP: offered, not tried

Surface audit: 275 documented operations: 212 run, 53 blocked by sandbox or plan limits and 10 left out because they spend money or reach real people. Of the 212 run, 195 passed and 17 didn't; 18 behaved differently from the docs. By surface, 112 in the CLI, 88 on the API, 7 on the MCP server and 5 elsewhere, such as sign-in and webhooks.

  • Holds up

    94of 100

    • Reliability100
    • Handles mistakes88

    The mean of the two.

  • Docs match

    86of 100

    • Docs accuracy92
    • Docs completeness71

    Docs accuracy counts 70%, completeness 30%.

  • Surface tested

    74of 100

    195 of 265 passed: the 275 documented operations less the 10 that spend money or reach real people

  • What it can't do, and why

    • Delete the account or organization No delete control in settings or docs; only a support ticket.
    • Create the first API key without the console The key API needs an existing key, so the first one comes from the browser.
    • Use TiDB Cloud Lake, Essential, Dedicated or changefeeds They need a paid plan with a saved card.
    • Run SQL through the ticloud shell command It refuses to run without a terminal.

12 of 16 other tasks done

  • Export data from an instanceDone
  • Create a SQL user for an instanceDone
  • Run a full-text searchDone
  • Expose data as an HTTPS endpoint with a Data AppDone
  • Allow an IP range to connect to an instanceDone
  • View built-in instance metricsDone
  • Checkpoint or fork a file system layerDone
  • Share a file system with a scoped tokenDone
  • Invite a member to the organizationDone
  • Change a member's roleDone
  • Read the console audit logDone
  • Read usage and costsDone
  • Restore an instance from a backupPaid plan
  • Create a manual backup of a Premium instancePaid plan
  • Stream changes to a downstream with a changefeedPaid plan
  • Create a TiDB Cloud Dedicated clusterThey need a paid plan with a saved card.Paid plan
  • Pause or resume a Dedicated clusterPaid plan
  • Change an Essential instance capacityPaid plan
  • Build a Lake dashboard from query resultsPaid plan
  • Schedule a SQL pipeline with Lake Task FlowPaid plan
  • Sync external data into Lake with an integration taskPaid plan
  • Set a spending limit on a Starter instancePaid plan
  • Set up organization SSOPaid plan
  • Connect over a private endpointBlocked
  • Mount a file system locallyBlocked
  • Connect an instance to Vercel or GitHubNot tried
  • Enable multi-factor authenticationNot tried

The drive used the free plan.

Tips for agent builders

From this drive

7 tips
  • Read the docs at docs.pingcap.com (llms.txt and .md pages); tidbcloud.com itself is closed to crawlers.
  • Use the hosted MCP at mcp.tidbcloud.com/mcp with the same key pair as HTTP Basic for read-only inspection and SELECT queries.
  • For ticloud import start of a CSV with a header row, leave out --csv.skip-header; with it the header is ignored and the columns become column_1, column_2.
  • Pass the full prefixed user name (prefix.user) to ticloud serverless sql-user delete; create and update add the prefix themselves, delete does not.
  • Install the pytidb MCP server with mcp<2 pinned; the documented uvx install pulls mcp 2.x and crashes.
  • Use ti db execute-sql-statement for browser-free SQL instead of the interactive shell.
  • Delete the last API key in the console; a key cannot delete itself through the API.

Pay

Paying

Ways to pay checked 4 Nov 2026.

  • ResultPartly. Reaches the checkout. A card form.
  • CheckoutReached the card form and stopped: Pay-as-you-go (Starter beyond free quota), $0 a call. It checks out through a Stripe card form. An invisible bot check loaded at checkout. It offers Link.

Leave

Leaving

  • ResultPartly. Nothing to cancel. It deletes its data, but the login stays.
  • Its accountNot all of it: it deletes its data, but the login stays. The login stays: all instances, branches, file systems, Data App, SQL users and every API key were deleted (the last key in the console, because the API refuses to let a key delete itself), and a call with the revoked key then got a 401. Neither the console nor the docs offer an account or organization delete; only a support ticket is left, which we do not send.

Daily checks

Checked every day

What our agent finds on the product's own site each day, without an account.

  • Sign-up page,

    Stopped on the newest check; 14 of 14 days

  • llms.txt (Its drive found one elsewhere),

    Not on its site on the newest check; 14 of 14 days

  • MCP server,

    Asks for a sign-in on the newest check; 4 of 14 days

  • OpenAPI,

    Found on the newest check; 4 of 14 days

Compare

How TiDB Cloud compares

In Databases

4 of the 21 products we drove in Databases are higher; 9 others share L3. As of 14 Nov 2026.

The products we drove in Databases, in the directory's order, with TiDB Cloud
ProductLevelFind to leave
UpstashL4Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own.
AirtableL4Find: Partly, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own.
NocoDBL4Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own.
ConvexL4Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: On its own.
Redis CloudL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
FirebaseL3Find: Partly, Get in: On its own, Use: Partly, Pay: Not tried, Leave: On its own.
NeonL3Find: On its own, Get in: On its own, Use: Partly, Pay: Not tried, Leave: On its own.
PlanetScaleL2Find: On its own, Get in: On its own, Use: Not measured, Pay: Partly, Leave: On its own.
BaserowL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
MongoDB AtlasL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
SupabaseL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
TiDB Cloud (this page)L3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.

12 of 21 shown, in the directory's order.

All 21 in DatabasesHow we rank

For the team behind TiDB Cloud

Agents get stuck at Pay

9 things to fix for agents: 6 small and 3 medium

One fix can cover several findings.

Agent blockers: 5 foundAgent surfaces: 20 issues found

Get your findings, freeWhat a drive covers

We mail a private link to an address at tidbcloud.com.

  1. FindClear
  2. Get inClear
  3. UseClear
  4. PayBlocks agents
  5. LeavePartly

Or claim TiDB Cloud to see where each issue is, read your safety findings with their fixes and ask for a free drive after a fix.

Want TiDB Cloud driven every month? See Watch

On our standard

Best or ahead on 7 of 28 criteria, behind on 5. Each against the other databases products we measured on it.

All 28 criteria
How each criterion is graded

Where TiDB Cloud fits

History

Level by drive

One drive so far, on 4 Nov 2026.

Source: our drives of TiDB Cloud. As of 4 Nov 2026.
  1. 11 Nov 2026Level L4 → L3Re-scored under method v47, drive of 4 Nov 2026

Read more on this step

Pay is where our agent stopped at TiDB Cloud.

Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.

Found an error? or read how corrections work.

Questions people ask about TiDB Cloud

Can an AI agent create a TiDB Cloud account on its own?
Yes, in a browser, without a person. Email and password form at tidbcloud.com/free-trial filled in the drive's browser; no CAPTCHA, no phone. Google, GitHub, Microsoft and AWS Marketplace sign-ins were offered and not used. There is no sign-up API, auth.md or claimable resource.
Does TiDB Cloud have an MCP server, and can an agent connect to it?
Yes. TiDB Cloud has an official MCP server. The server runs on the agent's own machine and lists 7 tools. A new agent can get in on its own: in the drive of 4 Nov 2026, our agent signed up, verified and got its key without a person. Through the MCP server, our agent tried 5 tasks and did 5.
How does an AI agent get a TiDB Cloud API key?
In the drive of 4 Nov 2026, our agent got its TiDB Cloud API key in a browser, without a person. The first API key (Organization Owner) can only be created in the console (Org Settings > API Keys); later keys came without a browser from the IAM API (POST iam.tidbapi.com/v1beta1/apikeys) and were used and revoked. ticloud auth login (OAuth device code) also works after two consent clicks in the browser.
Can an AI agent delete its TiDB Cloud account?
Not all of it: it deletes its data, but the login stays. The login stays: all instances, branches, file systems, Data App, SQL users and every API key were deleted (the last key in the console, because the API refuses to let a key delete itself), and a call with the revoked key then got a 401. Neither the console nor the docs offer an account or organization delete; only a support ticket is left, which we do not send.
Can an AI agent pay for TiDB Cloud?
Partly. Our agent reached a card form.

Cite this page

The page as a reference, in plain text, APA and BibTeX.

Cite this
Plain
AgentDrives, “TiDB Cloud: AI agent test drive”, 4 November 2026, https://agentdrives.com/tools/tidbcloud. CC BY 4.0.
APA
AgentDrives. (2026, November 4). TiDB Cloud: AI agent test drive. https://agentdrives.com/tools/tidbcloud
BibTeX
@misc{agentdrives_tidbcloud_2026,
  author = {{AgentDrives}},
  title = {TiDB Cloud: AI agent test drive},
  year = {2026},
  month = nov,
  url = {https://agentdrives.com/tools/tidbcloud},
  note = {Agent test drive, CC BY 4.0},
}

Something wrong on this page?

We check it against the drive and correct the page, with the date.