SkillAgentSearch skills...

dbento

Free, open-source native Rust database client: GPUI desktop app, CLI and read-only-by-default MCP server for Postgres, SQLite, MySQL, SQL Server, DuckDB, SurrealDB, MongoDB, Redis and DynamoDB.

Install / Use

claude mcp add PhongGuy -- npx -y github:PhongGuy/dbento

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

74/100

Supported Platforms

Claude Code
Claude Desktop

Our assessment of dbento

dbento scores 74/100 on our quality scale, 549th of 606 Data & Analytics skills we index.

Its MCP Server is 27 KB long, well organised into 29 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so dbento is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

dbento compared with similar skills

All 4 of these similar skills score higher than dbento; compare them before choosing.

SkillScoreStarsUpdatedFormat
dbento (this skill)by PhongGuy743todayMCP Server
claude-memby thedotmack100118.0ktodayCLAUDE.md
Agent-Reachby Panniantong100112.8k10d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md

Frequently asked questions

How do I install dbento?
Run claude mcp add PhongGuy -- npx -y github:PhongGuy/dbento. The install tabs above show the steps for each supported agent.
Which AI agents does dbento work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is dbento safe to use?
It is Apache-2.0-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is dbento still maintained?
The repository was last updated today, so dbento is actively maintained.

<img src="assets/icon/dbento-32.svg" alt="" width="40" height="40" align="top"> Dbento

A fast, native database client. Dbento is free and open source, written in Rust and drawn on the GPU: no Electron, no webview. It comes as a desktop app, a command line, and an MCP server that gives an AI client read-only access to your databases by default. It speaks SQL to Postgres, SQLite, MySQL, SQL Server and DuckDB, and each NoSQL store's own language to MongoDB, SurrealDB, Redis and DynamoDB. The name is db + bento: data in neat compartments.

Dbento with the demo shop open: the explorer on the left, a saved query in the editor and its result in the grid

Why Dbento

  • Native and fast. The desktop app is built on GPUI and rendered through the GPU. Results stream into a virtualized grid, so a large result scrolls as smoothly as a small one.
  • Your workspace is a folder. Connections live in dbento.toml and saved queries in plain text files, so a team can review them in git. No password is ever written to a file.
  • The database enforces safety. A read-only connection is opened read-only by the database itself, rather than by Dbento guessing from the SQL whether a statement writes.
  • AI access with you in the loop. The MCP server is read-only by default. A write runs only after you approve that exact call in the desktop app, and the AI can never approve itself.

Supported databases

| Database | engine in dbento.toml | Query language | Saved query files | | --- | --- | --- | --- | | PostgreSQL | postgres | SQL | .sql | | SQLite | sqlite | SQL | .sql | | MySQL and MariaDB | mysql (or mariadb) | SQL | .sql | | SQL Server | mssql (or sqlserver) | T-SQL | .sql | | DuckDB | duckdb | SQL | .sql | | MongoDB | mongodb (or mongo) | a subset of mongosh: find, aggregate, insertOne, updateMany and more | .js | | SurrealDB | surrealdb (or surreal) | SurrealQL, over WebSocket | .surql | | Redis and Valkey | redis (or valkey) | Redis commands, one per line | .redis | | Amazon DynamoDB | dynamodb (or dynamo) | PartiQL | .partiql |

DuckDB, MongoDB, SurrealDB, Redis and DynamoDB are default Cargo features (duckdb, mongodb, surrealdb, redis, dynamodb) of the core, the command line, the MCP server and the app. A build with --no-default-features leaves them out, and leaving out DuckDB skips its C++ compile. Other engines are tracked in the issue tracker.

Features

A result grid that keeps up

Results stream in as the database sends them, into a virtualized grid that fetches the next batch as you scroll. A row limit (1k, 10k, 100k or 1M rows, or none, with only a memory budget) stops collecting and marks the result truncated. Dbento never rewrites your SQL to add a LIMIT, and a type it does not know is shown, never turned into NULL. Copy cells as TSV, CSV, JSON, Markdown or INSERT statements, export loaded rows to CSV, TSV or JSON, and step through one row in the record view.

An editor that knows your schema

SQL highlighting, formatting, and completion of schemas, tables, columns and keywords from the connection's live catalog. Queries open in tabs, saved queries are plain .sql files, every run lands in a searchable history, and the command palette (Ctrl+P, Cmd+P on macOS) finds tables, saved queries and commands. Ctrl+/ (Cmd+/) toggles line comments, a tab with unsaved changes is marked and asks before it closes, and a running query can be cancelled.

Completion in a WHERE clause offering the columns of orders, the customers table and SQL keywords

An explorer down to the indexes

The schema tree shows tables, views, materialized views and foreign tables, and under each one its columns, keys, indexes, checks and triggers, plus types and routines on Postgres and SQL Server and routines on MySQL. Open an object to read its definition, where the engine gives one, copy it, or open it in a query tab.

The orders table expanded in the explorer, with its index's CREATE INDEX statement in the definition dock

Documents, keys and items

The NoSQL stores share the same explorer, editor and grid, each in its own language.

  • MongoDB: databases and collections, with fields inferred from a sample of documents, and indexes. Opening a collection runs its find(). Columns come from the first documents, and fields that appear later land in a (more fields) column.
  • Redis and Valkey: each DB index with its key count, and the keys grouped into folders by :. Keys are listed with a SCAN walk that shows each key's type and TTL, and the filter takes a pattern plus type:<kind>. Opening a string, hash, list, set, sorted set or stream shows its value in a paged grid, with its type, length and TTL. Command completion comes from the server's COMMAND DOCS.
  • DynamoDB: one schema per region, with tables, their key attributes, indexes, and attributes sampled from items. Opening a table or an index runs a PartiQL SELECT, and attributes beyond the first items land in a (more attributes) column.
  • SurrealDB: the namespace's databases and their tables, read from INFO and sampled rows, with fields, indexes and triggers. Opening a table runs SELECT * FROM it.

Editing you review before it lands

Edit cells, add rows and delete rows in a browsed Postgres or SQLite table. Changes are staged, then applied in one transaction with typed parameters, after a prompt that says how many rows they affect and asks you to commit or roll back. Rows without a primary key are found by ctid and xmin on Postgres and by rowid on SQLite, and a row someone else changed or deleted in the meantime is marked instead of overwritten.

Two staged price changes on products and the prompt: affects 2 rows, roll back or commit

AI access through MCP

dbento mcp serves a workspace to an AI client over MCP on stdio, with ten tools: list_connections, list_databases, list_schemas, list_tables, describe_table, query, explain, list_saved_queries, read_saved_query and execute.

  • query always runs read-only, one statement in the connection's own language: SQL, a mongosh statement, SurrealQL, one Redis command, or PartiQL. Redis commands in the @dangerous, @blocking, @scripting and @pubsub categories are refused. It returns 100 rows by default and at most 1,000, about 64 KiB, under a statement timeout of 30 seconds by default.
  • explain shows the plan of one statement on Postgres and SQLite in the same read-only session, so an AI can preview an UPDATE or DELETE without running it. ANALYZE is refused.
  • list_saved_queries and read_saved_query read the saved query files (.sql, .js, .surql, .redis, .partiql) under the workspace's queries/ folder and nothing outside it, not even through a symlink.
  • execute waits until you approve that exact call in the desktop app, once. When you deny a call you can type a reason, and the AI gets it back with the denial.

Query results are passed to the AI as untrusted data. The app's approvals panel shows the command to connect your AI client.

The app asking whether to approve an AI's UPDATE on the shop connection

Safety the database enforces

  • A read_only connection runs every statement in BEGIN READ ONLY on Postgres and opens SQLite and DuckDB read-only, so the database itself refuses a write. A read_only DuckDB connection also has file access off, so read_csv and Parquet reads of local files do not work there.
  • On Postgres the server still lets a few things through: functions that open their own connections, such as dblink_exec where the dblink extension is installed, and admin functions whose effect is not transactional, such as pg_terminate_backend, pg_cancel_backend and pg_stat_reset. For a production database, use a role without the privileges the rest need; it can still cancel or terminate backends of its own role.
  • A MySQL or MariaDB read_only connection, and every MCP session on one, runs each statement in START TRANSACTION READ ONLY. The server still lets a few things through: SELECT ... INTO OUTFILE or DUMPFILE, SET GLOBAL and SET PERSIST, FLUSH, GET_LOCK, and an existing stored procedure that commits and then writes. For a production database, use an account without the FILE, RELOAD, SYSTEM_VARIABLES_ADMIN or SUPER privileges and without EXECUTE on such procedures, ideally one granted only SELECT.
  • On SQL Server, give a read_only connection a read_only_user (a login that can only read) and the database enforces it. Without one the session is best effort: Dbento fences each batch in a transaction it rolls back and refuses the batches it can parse as writes, but a login with the rights can get past the fence with a hidden commit. list_connections states the level of each connection to an AI client.
  • On MongoDB, Dbento reads the user's privileges when it connects. A user that can only read is enforced by the server; for any other user Dbento refuses every command it cannot show reads.
  • On SurrealDB each statement runs in a transaction that is cancelled, and a VIEWER login is enforced by the server. At either level, stored logic reached from a SELECT can still advance sequences, call http::* functions or write files, and a root OWNER or anonymous login can run ALTER SYSTEM.
  • On Redis and Valkey, Dbento checks the user's ACL against the server's command table when it connects. A user whose ACL refuses every write is enforced by the server; otherwise Dbento refuses writes and commands it cannot classify. The check runs once, so a later ACL SETUSER can widen the user.
  • DynamoDB has no read-only session. A read-only connection sends only ListTables, DescribeTable, Scan and PartiQL SELECT, but only IAM stops someone with the same keys from writing, so give a production connection keys that can only read.
  • A connection tagged red, or in a red folder, is marked as production in its query tab's toolbar and the status bar.
  • UPDATE or DELETE without WHERE, DROP (and MongoDB's drop or SurrealDB's REMOVE), TRUNCATE, updateMany or deleteMany with an empty filter, and FLUSHDB or FLUSHALL ask before they run. DynamoDB statements never ask.
  • Write detection follows each engine: pg_query for Postgres and DuckDB, so a write hidden in a CTE is still caught; SQLite's own read-only check; sqlparser for MySQL and SQL Server; an allowlist of read methods for MongoDB; the server's command table for Redis; a keyword scan for SurrealDB; and the first keyword of a PartiQL statement for DynamoDB. Outside a read-only session, a statement the parser cannot handle is never blocked for that reason alone.

Also

  • Light and dark themes, or follow the system.
  • Shortcuts can be rebound in a keymap.json, which Settings (Ctrl+,) opens and reloads.
  • dbento import datagrip, dbento import dbeaver and dbento import beekeeper bring over connections and saved queries from DataGrip, DBeaver and Beekeeper Studio, and saved passwords go to the keychain.
  • The app checks for a new release at most once a day, and Settings has a switch to turn that off and a Check now button (also Ctrl+K U, or "Check for updates" in the palette). A banner offers the release or lets you skip it; the download is verified against a signed manifest and installed when you quit. This works for the AppImage, the macOS .app and the Windows installer. The .deb and anything else under /usr, builds from source, and a copy running from the mounted disk image are left to you.
  • dbento self-update checks for a newer release and replaces a standalone dbento download in place; --yes skips the question, and --check only reports (it exits 2 when

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategoryData
Updated5h ago
Forks1

Languages

Rust

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low