Skip to main content
libSQL is an open-source fork of SQLite with added features like a server mode and replication. It’s SQLite-compatible, so QueryBear queries it through the same read-only security gateway used for local SQLite.

​
Connection options

libSQL can run in several modes:
  1. Local file — a libSQL/SQLite file on disk. Point QueryBear at the file path, exactly like local SQLite.
  2. Server mode (sqld) — libSQL running as a server, reachable over an http:// or libsql:// URL, optionally with an auth token.
  3. Hosted (Turso) — see the dedicated Turso integration.

​
Add the connection to QueryBear

In the QueryBear dashboard → Connections → New connection → SQLite / libSQL:
  • Local file: provide the absolute path to the .db / libSQL file.
  • Server mode: provide the http:// / libsql:// URL (and auth token if your sqld requires one).

​
libSQL-specific notes

  • Read-only enforced at the QueryBear gateway. If your sqld server supports read-only tokens, use one for defense in depth.
  • ATTACH DATABASE is blocked at the parser.
  • SQLite feature parity: JSON1 functions, FTS5 virtual tables, and views all work.

​
Connect to your AI client

Identical to local SQLite: