NocoDB vs Turso for AI agents
As of 6 Oct 2026, NocoDB gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 100% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Through every checkpoint. Next: pay without a person
L4 · Runs on its own: our agent signed up and confirmed through a browser form and an emailed code, then worked headless from a token. No checkpoint stopped it: tokens and MCP keys needed a settings page, not an API, and some REST groups stayed plan-gated or unreachable with any token. Through the official MCP server and the REST API it created bases, tables, fields, records, views, sharing, CSV import, workflows, interfaces and dashboards, and NocoAI built a table from one sentence in the web app. Upgrading opens an embedded Stripe checkout with an invisible hCaptcha and HUMAN Security our agent never tried; it deleted its account cleanly from Account settings, and its token and MCP key stopped working right after.
Gets furtherDriven 3 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person: L1 · Needs a person. Our agent read Turso's docs on its own, headless, with llms.txt and Markdown pages, then hit a Clerk web form for sign-up. Submitting it showed a visible Cloudflare Turnstile check our agent could not pass, so no account, token or cloud database followed, and every API path answered that no token was present. Through the API it reached nothing live, but the embedded engine ran locally through the official SDK with no account at all: SQL, vectors, full-text search and CDC all worked there. Paying and leaving were never reached: no plan was started and no account existed to delete.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
NocoDBThrough every checkpoint
TursoStopped at sign up: needs a human
| Checkpoint | NocoDB | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Needs a human |
| Verify | In a browser | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| NocoDB | Turso | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 5 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 100% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| NocoDB | Turso | |
|---|---|---|
| Bot check | None met | Cloudflare Turnstile (via Clerk bot protection) stopped it at sign up, with a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | None | Cloudflare Turnstile on the sign-up form |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| NocoDB | Turso | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Holds up | 59 of 100, fair | Not measured |
| Docs match | 59 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | MCP client registration (current) · OpenAPI 3.0.1 (2 versions behind) · A2A 0.3 (1 version behind) |
| Security | Reported privately to the owner | No review in this drive |
Pay, cancel and delete.
| NocoDB | Turso | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- NocoDB: Reaches the checkout: stopped at the card form.
- Turso: Payment not reached.
NocoDB vs Turso: the short answers.
Which can an AI agent use, NocoDB or Turso?
NocoDB gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With NocoDB our agent went through every checkpoint; with Turso it was stopped at sign up (needs a human). Driven 3 Oct 2026 (NocoDB) and 6 Oct 2026 (Turso).
Can an AI agent sign up for NocoDB and Turso on its own?
NocoDB: yes, in a browser. Turso: no, needs a human.
Do NocoDB and Turso have an MCP server?
NocoDB: yes (official). Turso: yes (official).
Can an AI agent delete its NocoDB or Turso account?
NocoDB: yes, in a browser. Turso: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.