Skip to content

How Turso’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score37/100

Agent-ready 74.4 × 0.30 = 22.32

API quality 11.4 × 0.20 = 2.28

Openness 29.4 × 0.20 = 5.88

Built-in AI 24.4 × 0.15 = 3.66

Automation 21.3 × 0.15 = 3.19

(22.32 + 2.28 + 5.88 + 3.66 + 3.19) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 37.34 ÷ 1.00 = 37.3

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready74.4/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [probe] https://docs.turso.tech/llms.txtPROBE llms.txt: HTTP 200 at https://docs.turso.tech/llms.txt # Turso ## Docs - [Welcome to Turso](https://docs.turso.tech/introduction.md): The small database to power your big dr
  • [probe] https://docs.turso.tech/introduction.mdPROBE docs-md: HTTP 200 at https://docs.turso.tech/introduction.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.turso.tech/llms.txt > Use this file t

Run the product headlessly / in CI for automationweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/quickstartturso db create my-db --tursodb
  • [claimed-docs] https://docs.turso.tech/quickstartNow connect to it with the `shell` command:
  • [claimed-docs] https://docs.turso.tech/local-developmentThis will start a local libSQL server and create a database for you.
  • [claimed-docs] https://docs.turso.tech/features/branchingAutomating branching is useful for creating a new database for each pull request.
  • [claimed-docs] https://docs.turso.tech/sdk/ts/quickstartPush local writes to Turso Cloud await db.push(); // Pull remote changes to local database const changed = await db.pull();
  • [probe] https://docs.turso.tech/cli/introductionPROBE runtime (recorded 2026-09-06): the official Turso CLI installed via the vendor's get.tur.so installer and `turso --version` printed `turso version v1.0.32` keylessly; the installer also ships the sqld libSQL server binary for local development.
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.
  • [probe] https://docs.turso.tech/cli/introductionofficial CLI documented at https://docs.turso.tech/cli/introduction

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Connect an agent via an official MCP serverweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpThere’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf.
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Use an official CLIweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [probe] https://docs.turso.tech/cli/introductionofficial CLI documented at https://docs.turso.tech/cli/introduction
  • [probe] https://docs.turso.tech/cli/introductionPROBE runtime (recorded 2026-09-06): the official Turso CLI installed via the vendor's get.tur.so installer and `turso --version` printed `turso version v1.0.32` keylessly; the installer also ships the sqld libSQL server binary for local development.
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.
  • [claimed-docs] https://docs.turso.tech/quickstartturso db create my-db --tursodb
  • [claimed-docs] https://docs.turso.tech/quickstartNow connect to it with the `shell` command:
  • [claimed-docs] https://docs.turso.tech/quickstartturso db shell my-db
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://turso.techSpin up thousands or millions of isolated databases programmatically, each with its own boundary. Not a workaround. The architecture.
  • [claimed-docs] https://turso.techSQLite-compatible. SDKs in TypeScript, Python, Rust, and Go. Self-serve from signup to production.
  • [probe] https://docs.turso.tech/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.turso.tech/openapi.json, https://docs.turso.tech/swagger.json, https://docs.turso.tech/api/openapi.json, https://docs.turso.tech/.well-known/openapi.json)
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf.
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Build against official SDKsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [claimed-docs] https://turso.techSQLite-compatible. SDKs in TypeScript, Python, Rust, and Go. Self-serve from signup to production.
  • [claimed-docs] https://docs.turso.tech/sdk/ts/quickstartpush() sends your changes to the cloud. pull() brings remote changes down.
  • [claimed-docs] https://docs.turso.tech/sdk/ts/quickstartPush local writes to Turso Cloud await db.push(); // Pull remote changes to local database const changed = await db.pull();
  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Subscribe to events via webhooksweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Agent-ready = 134.0 ÷ 180 × 100 = 74.4

API quality11.4/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [probe] https://docs.turso.tech/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.turso.tech/openapi.json, https://docs.turso.tech/swagger.json, https://docs.turso.tech/api/openapi.json, https://docs.turso.tech/.well-known/openapi.json)

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://docs.turso.tech/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.turso.tech/openapi.json, https://docs.turso.tech/swagger.json, https://docs.turso.tech/api/openapi.json, https://docs.turso.tech/.well-known/openapi.json)
  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 8 (quality) × 1.0 (full) = 8.0 of 10 max

  • [claimed-docs] https://docs.turso.tech/features/branchingBranches are useful for development and testing, because they allow you to make changes to the database without affecting the original database.
  • [claimed-docs] https://docs.turso.tech/features/branchingturso db create my-new-database-branch --from-db my-existing-database
  • [claimed-docs] https://docs.turso.tech/features/branchingA branch is a separate database instance that is created from an existing database.
  • [claimed-docs] https://docs.turso.tech/features/branchingA branch is a separate database instance that is created from an existing database... Branches are useful for development and testing, because they allow you to make changes to the database without affecting the original database.
  • [claimed-docs] https://docs.turso.tech/features/branchingAutomating branching is useful for creating a new database for each pull request.
  • [claimed-docs] https://docs.turso.tech/local-developmentYou can always dump your production database and use it locally for development
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://docs.turso.tech/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.turso.tech/openapi.json, https://docs.turso.tech/swagger.json, https://docs.turso.tech/api/openapi.json, https://docs.turso.tech/.well-known/openapi.json)

API quality = 8.0 ÷ 70 × 100 = 11.4

Openness29.4/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/quickstartturso db create my-db --tursodb
  • [claimed-docs] https://docs.turso.tech/features/branchingturso db create my-new-database-branch --from-db my-existing-database
  • [probe] https://docs.turso.tech/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.turso.tech/openapi.json, https://docs.turso.tech/swagger.json, https://docs.turso.tech/api/openapi.json, https://docs.turso.tech/.well-known/openapi.json)
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Export all of my data in open formats and leaveweight 3

3 (weight) × 4 (quality) × 0.3 (disputed) = 3.6 of 30 max

  • [claimed-docs] https://docs.turso.tech/local-developmentturso db shell your-database .dump > dump.sql
  • [claimed-docs] https://docs.turso.tech/local-developmentYou can always dump your production database and use it locally for development
  • [claimed-docs] https://docs.turso.tech/introductionFully backwards compatible with SQLite, but built for the next generation
  • [claimed-docs] https://turso.techSQLite-compatible. SDKs in TypeScript, Python, Rust, and Go. Self-serve from signup to production.
  • [community] https://hn.algolia.com/api/v1/items/46677583You're only file format compatible if you don't use any of the Turso extensions. As soon as you use an unsupported feature in your schema... the SQLite CLI no longer works, Litestream doesn't work, sqlite_rsync doesn't work, recovery tools don't work, SQLite UIs don't work.
  • [community] https://hn.algolia.com/api/v1/items/46677583I don't trust an open-source project once it's backed by a VC firm... At this point 'compatible with SQLite' has become a marketing term IMO, we all know how easy it is to break compatibility here.

Read the product's source under an open licenseweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

  • [community] https://hn.algolia.com/api/v1/items/43535943disclosure: I work at Turso. libSQL is our fork of SQLite. It adds new features on top of SQLite, such as vector search, replication, server mode, and more. libSQL is open source (MIT license).
  • [probe] https://docs.turso.tech/cli/introductionofficial CLI documented at https://docs.turso.tech/cli/introduction
  • [probe] https://docs.turso.tech/cli/introductionPROBE runtime (recorded 2026-09-06): the official Turso CLI installed via the vendor's get.tur.so installer and `turso --version` printed `turso version v1.0.32` keylessly; the installer also ships the sqld libSQL server binary for local development.

Self-host the core productweight 3

3 (weight) × 7 (quality) × 0.6 (partial) = 12.6 of 30 max

  • [claimed-docs] https://docs.turso.tech/local-developmentLocal Turso database — local database file, no server needed (recommended)
  • [claimed-docs] https://docs.turso.tech/local-developmentThis will start a local libSQL server and create a database for you.
  • [claimed-docs] https://docs.turso.tech/local-developmentThey are fully SQLite-compatible — they open existing SQLite files — and run entirely in your process, no server needed
  • [community] https://hn.algolia.com/api/v1/items/43535943disclosure: I work at Turso. libSQL is our fork of SQLite. It adds new features on top of SQLite, such as vector search, replication, server mode, and more. libSQL is open source (MIT license).
  • [probe] https://docs.turso.tech/cli/introductionPROBE runtime (recorded 2026-09-06): the official Turso CLI installed via the vendor's get.tur.so installer and `turso --version` printed `turso version v1.0.32` keylessly; the installer also ships the sqld libSQL server binary for local development.
  • [probe] https://docs.turso.tech/local-developmentPROBE runtime (recorded 2026-09-06): `turso dev --db-file /tmp/pa-turso-probe.db --port 8085` booted a fully keyless local libSQL server (sqld listening on port 8085) and a REAL SQL roundtrip ran over the Hrana HTTP pipeline API — CREATE TABLE, INSERT id 6, SELECT id*7 returned {"type":"integer","value":"42"} — no account, no cloud dependency.
  • [community] https://hn.algolia.com/api/v1/items/46677583You're only file format compatible if you don't use any of the Turso extensions. As soon as you use an unsupported feature in your schema... the SQLite CLI no longer works, Litestream doesn't work, sqlite_rsync doesn't work, recovery tools don't work, SQLite UIs don't work.
  • [community] https://hn.algolia.com/api/v1/items/46677583Looks like it's still missing some important features like savepoints (!!!), windows and attach database.

Openness = 29.4 ÷ 100 × 100 = 29.4

Built-in AI24.4/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf.
  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [claimed-docs] https://docs.turso.tech/features/branchingAutomating branching is useful for creating a new database for each pull request.
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Operate the product with natural-language commandsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpThere’s no API token to copy or paste.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf.
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Built-in AI = 22.0 ÷ 90 × 100 = 24.4

Automation21.3/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

  • [claimed-docs] https://docs.turso.tech/api-reference/introductionProvision a dedicated database per user or per AI agent. Each entity gets its own isolated SQLite database that you create, token-scope, and tear down via the API.
  • [claimed-docs] https://turso.techSpin up thousands or millions of isolated databases programmatically, each with its own boundary. Not a workaround. The architecture.
  • [claimed-docs] https://turso.techSQLite-compatible. SDKs in TypeScript, Python, Rust, and Go. Self-serve from signup to production.

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://docs.turso.tech/features/branchingAutomating branching is useful for creating a new database for each pull request.

Schedule recurring jobs or workflowsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

1 (weight) × 5 (quality) × 0.6 (partial) = 3.0 of 10 max

  • [claimed-docs] https://docs.turso.tech/features/branchingBranches are useful for development and testing, because they allow you to make changes to the database without affecting the original database.
  • [claimed-docs] https://docs.turso.tech/features/branchingAutomating branching is useful for creating a new database for each pull request.
  • [claimed-docs] https://docs.turso.tech/features/branchingturso db create my-new-database-branch --from-db my-existing-database
  • [claimed-docs] https://docs.turso.tech/features/point-in-time-recoveryPITR allows you to restore a database to a specific point in time. This is useful for recovering from user errors, such as dropping a table by mistake.
  • [claimed-docs] https://docs.turso.tech/features/point-in-time-recoveryTurso supports point-in-time recovery (PITR) for databases. PITR allows you to restore a database to a specific point in time.
  • [claimed-docs] https://docs.turso.tech/features/point-in-time-recoveryTurso supports point-in-time recovery (PITR) for databases. PITR allows you to restore a database to a specific point in time. This is useful for recovering from user errors, such as dropping a table by mistake.
  • [claimed-docs] https://docs.turso.tech/integrations/mcpConnect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf... There’s no API token to copy or paste.
  • [probe] https://docs.turso.tech/integrations/mcpofficial MCP server documented at https://docs.turso.tech/integrations/mcp
  • [probe] https://docs.turso.tech/integrations/mcpPROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.turso.ai/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.turso.ai/.well-known/oauth-protected-resource/mcp — the documented OAuth-based agent endpoint (manage databases, branch, run SQL) is live.

Automation = 17.0 ÷ 80 × 100 = 21.3