# Best databases for AI agents: 6 of 16 run on their own

We drove 16 databases with a real agent: which ones it could create on its own, how far it got, and every MCP server, tested or documented.

Source: https://agentdrives.com/research/best-databases-for-ai-agents?via=md · Updated 2026-11-03 · 16 products, driven 2026-10-03 to 2026-11-02

As of 2 November 2026, Upstash, Prisma Postgres and Neon gave our agent a working hosted database with no account at all, and Airtable, NocoDB and Couchbase did after a sign-up it made itself in a browser. 6 of 16 databases took our agent all the way to [L4 Runs on its own](/method): it got in without a person and did every core task.

## The ranking: every database our agent got into

10 of 16 let our agent in on its own, Convex, Firebase and Redis Cloud on a local edition with no account. In rank order, the same as on [Databases](/categories/databases):

| Database | Level | Where it stopped | Got in | Core work |
|---|---|---|---|---|
| [Upstash](/tools/upstash) | Runs on its own | Monthly charge | No account | All |
| [Prisma Postgres](/tools/prisma) | Runs on its own | Monthly charge | No account | All |
| [Airtable](/tools/airtable) | Runs on its own | Monthly charge | Signed up | All |
| [Convex](/tools/convex) | Runs on its own | Needs an account | Runs locally | All |
| [NocoDB](/tools/nocodb) | Runs on its own | Card form | Signed up | All |
| [Couchbase](/tools/couchbase) | Runs on its own | Card form | Signed up | All |
| [Firebase](/tools/firebase-google) | Does the work | Needs an account | Runs locally | Part |
| [Neon](/tools/neon) | Does the work | Pay not reached | No account | Part |
| [Redis Cloud](/tools/redis) | Does the work | A CAPTCHA | Runs locally | Part |
| [PlanetScale](/tools/planetscale) | Gets in | Card before a database | Signed up | Not measured |

The other 6 of 16 stopped it at sign-up and share last place, each at a wall [named below](#where-sign-up-stopped-our-agent). See [how we order lists](/method#order).

## Which databases have an MCP server

15 of 16 databases we drove have an MCP server for the product. Tested: our agent called it in its drive. Documented: the vendor publishes it; our agent didn't call it.

| Database | MCP server | In our drive | Signs in with |
|---|---|---|---|
| [Upstash](/tools/upstash) | `mcp.upstash.com/mcp` | Tested | OAuth, or an API key in a header |
| [Prisma Postgres](/tools/prisma) | `mcp.prisma.io/mcp` | Tested | OAuth; admin and production writes wait for a person's approval |
| [Airtable](/tools/airtable) | `mcp.airtable.com/mcp` | Tested | OAuth consent |
| [Convex](/tools/convex) | `mcp.convex.dev/mcp` | Tested | Hosted guidance server; the CLI's server needs a Convex login |
| [NocoDB](/tools/nocodb) | `app.nocodb.com/mcp` | Tested | A NocoDB account |
| [Couchbase](/tools/couchbase) | [Self-hosted server](https://github.com/couchbase/mcp-server-couchbase) | Tested | Your Capella cluster's credentials |
| [Firebase](/tools/firebase-google) | [Local server in the Firebase CLI](https://firebase.google.com/docs/ai-assistance/mcp-server) | Documented | The Firebase CLI's login |
| [Neon](/tools/neon) | `mcp.neon.tech/mcp` | Documented | OAuth, or a Neon API key |
| [Redis Cloud](/tools/redis) | [Local server, mcp-redis](https://github.com/redis/mcp-redis) | Tested on local Redis | Your Redis connection |
| [PlanetScale](/tools/planetscale) | `mcp.pscale.dev/mcp/planetscale` | Tested | OAuth, or a service token as a Bearer header |
| [Appwrite](/tools/appwrite) | `mcp.appwrite.io/mcp` | Tested on the self-hosted edition | OAuth; the local server takes an API key |
| [Baserow](/tools/baserow) | `api.baserow.io/mcp` | Tested on the self-hosted edition | OAuth, or an endpoint key |
| [MongoDB Atlas](/tools/mongodb) | `mcp.mongodb.com` | Tested on local MongoDB | OAuth; the local server takes a connection string |
| [Supabase](/tools/supabase) | `mcp.supabase.com/mcp` | Tested on the self-hosted edition | OAuth |
| [Turso](/tools/turso) | `mcp.turso.ai/mcp` | Documented | OAuth, with no device flow |
| [CockroachDB](/tools/cockroachlabs) | [Cloud MCP server](https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server) | Docs server only | OAuth or an API key, from a Cloud account |

CockroachDB is the one not counted: the server our agent reached, `https://docs.cockroachlabs.com/mcp`, only searches its docs. Redis runs a docs server too, at `https://redis.io/mcp`.

## Verdicts, database by database

**Upstash: best for Redis an agent starts by itself.** In under a minute, with no account, [start-redis](https://upstash.com/start-redis) answered with an endpoint and a REST token. With an account and one MCP consent click, every core product worked.

**Prisma Postgres: best for Postgres with no CAPTCHA anywhere.** `npx create-db` gave a database with no account; after a plain email sign-up, our agent made its own service token over the API and did every core task.

**Airtable: best for records a person also reads.** Bases, records, automations, webhooks and forms all worked after a browser sign-up.

**Convex: best for a full app backend with no account.** Database, functions, live updates, file storage and user login all ran locally, with no login or deploy key.

**NocoDB: best for a spreadsheet database on a free plan.** Its MCP server covered views, dashboards and workflows that its REST API doesn't.

**Couchbase: best for document data with vector search.** One API key made in the web UI opened every core task, vector search and mobile sync included.

**Firebase: best for local development.** The emulator ran Firestore, Auth, Storage and Functions; a live project needs a Google account.

**Neon: best for throwaway Postgres before a person exists.** SQL, app user sign-up, reads and writes, all on an unclaimed database.

**Redis Cloud: open Redis works; the cloud console wants a person.** Every console login met a press-and-hold check, and Cloud API keys are made only there. Redis Open Source with its MCP server did keys, hashes, full-text and vector search.

**PlanetScale: gets an agent in, then asks for a card.** Sign-up from the CLI and the MCP sign-in went through; every database needs a card on file.

## Ways in made for agents

Each of these worked for our agent with no account.

| Database | Way in | What it needs |
|---|---|---|
| [Upstash](https://upstash.com/start-redis) | start-redis | Nothing: a scratch Redis that expires |
| [Prisma Postgres](https://www.prisma.io/docs/postgres/npx-create-db) | `npx create-db` | Nothing |
| [Neon](https://neon.com/docs/reference/claimable-neon) | Claimable Neon | Nothing; a person claims it later |
| [Convex](https://docs.convex.dev/cli/agent-mode) | CLI agent mode | No login or deploy key; runs locally |

Neon's docs: “If an agent needs a Neon account and the user is not around, provision a project now; they claim it later.” ([source](https://neon.com/docs/reference/claimable-neon))

## Where sign-up stopped our agent

At 6 of 16 databases, sign-up was the first step our agent didn't pass on its own. Baserow and Turso put Cloudflare Turnstile on the form, CockroachDB a reCAPTCHA and Supabase an hCaptcha. MongoDB Atlas's form refused our agent's browser, and Appwrite's robots.txt closes sign-up to AI agents.

Each of them ran anyway as an open-source, self-hosted or embedded edition with no account. The level, [L1 Needs a person](/method), is the hosted product's.

## Paying and leaving

Payment was the first step our agent didn't pass at 9 of 16, every database that runs on its own among them. Each checkout our agent reached wanted a card or a CAPTCHA, and Convex and Firebase take payment only from an account.

An agent could leave on its own at 9 of 16, with no plan to cancel.

## What a database owner can change

1. **Let an agent start before a person,** as Upstash, Prisma Postgres and Neon do.
2. **Take the bot check off sign-up,** the wall at Baserow, CockroachDB, Supabase and Turso.
3. **Issue keys over an API.** Redis Cloud and Upstash make theirs only in a console.
4. **Accept a payment an agent can make.** Every database that ran on its own stopped there.

## Sources

The ranking and the MCP table link each database's newest drive record, with its drive date. [Databases](/categories/databases) shows them side by side, and [our method](/method) sets the levels and the order.

Vendor pages: [Upstash start-redis](https://upstash.com/start-redis), [Prisma create-db](https://www.prisma.io/docs/postgres/npx-create-db), [Neon claimable projects](https://neon.com/docs/reference/claimable-neon), [Convex CLI agent mode](https://docs.convex.dev/cli/agent-mode), [Firebase MCP server](https://firebase.google.com/docs/ai-assistance/mcp-server), [Couchbase MCP server](https://github.com/couchbase/mcp-server-couchbase), [Redis MCP server](https://github.com/redis/mcp-redis), [CockroachDB Cloud MCP server](https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server), [MongoDB MCP server](https://github.com/mongodb-js/mongodb-mcp-server).

## Method and limits

- Products: 16, driven 2026-10-03 to 2026-11-02.
- Numbers: each one links to its definition and the products behind it.
- Limits: Cloudflare has listed our agent as a signed agent since 24 October 2026. Drives before 24 October 2026 ran signed but unlisted: a check could see the signature but had no listed identity to trust. No other bot-check provider lists it yet.
- Every number, with its products: [our facts](/data/facts). How we drive and score: [our method](/method).

## Questions

**Which database can an AI agent create on its own?**

Hosted with no account: Upstash for Redis, Prisma Postgres and Neon for Postgres. Hosted after a sign-up our agent made itself: Airtable, NocoDB and Couchbase. On its own machine, with no account: Convex, Firebase and Redis.

**Which databases have an MCP server?**

15 of 16 databases we drove have one. Upstash, Prisma Postgres, Airtable, NocoDB and Couchbase did core work through theirs in our drives; Neon, Firebase and Turso document one our agent didn't call.

**Where do agents get blocked when signing up for a database?**

At the sign-up form. That was the wall at 6 of 16, mostly a CAPTCHA or Cloudflare Turnstile; Appwrite's robots.txt closes its sign-up to AI agents.

**Can an AI agent pay for a database plan on its own?**

Not yet: 0 of 16. No checkout our agent reached took a payment it could make alone.

**Postgres, Redis or a reactive backend: which fits an agent-built app?**

For Postgres, Prisma Postgres did every core task, and Neon hands over a database with no account. For Redis, Upstash starts one with no account. For a reactive backend, Convex did every core task locally.