database-mcp-libsql 0.1.0

MCP server for libSQL/Turso (local files and remote databases) with read-only guardrails, row caps, and statement timeouts

database-mcp-libsql

MCP server giving AI clients safe, structured access to a libSQL database: a local file or a remote libSQL/Turso server. Two tools, guardrails on by default.

Quick start (Claude Desktop / Claude Code / Cursor)

{
  "mcpServers": {
    "libsql": {
      "command": "uvx",
      "args": ["database-mcp-libsql", "--dsn", "libsql://your-db.turso.io"],
      "env": { "LIBSQL_AUTH_TOKEN": "your-token" }
    }
  }
}

For a local file, use --dsn /absolute/path/to/database.db and skip the token.

Configuration

Connection

• Flag: --dsn <file-or-libsql-url>
• Environment: LIBSQL_URL
• Config file: connection.dsn in --config /path/to/database-mcp.yaml

Auth token (remote servers)

Three ways, strongest first:

• LIBSQL_AUTH_TOKEN_FILE=/run/secrets/token (file contents, never in the environment or any committed file)
• LIBSQL_AUTH_TOKEN=...
• In YAML: connection.password: ${LIBSQL_AUTH_TOKEN} (env expansion, never a literal)

The token is held in a non-printable type and redacted from all output.

Tools

• execute_sql: run a single SQL statement. Returns a summary line and compact JSON {columns, rows}.
• search_objects: list tables with estimated row counts, or describe one table (columns, indexes, foreign keys).

Guardrails

• Read-only by default, enforced twice: a SQL guard plus PRAGMA query_only = ON. Remote servers may not honor the pragma; use a read-only Turso token for real protection. Pass --allow-write to enable writes.
• Results capped at maxRows (default 1000, MAX_ROWS).
• Statements exceeding queryTimeoutMs (default 30000, QUERY_TIMEOUT_MS) are aborted.

Full contract: docs/tool-contract.md

---

mcp-name: io.github.arifulislamat/database-mcp-libsql