Changelog
Release notes for the safe-db desktop app and the safe-db MCP server.
1.1.1
LatestThe desktop app, the MCP server, and the shared query engine.
- Query timeout. Settings accepts a whole number of seconds from 1 to 120.
The default is 10. It applies to the next desktop or MCP query run and to the plan check
before that run. Connect and schema introspection stay on their fixed limits.
safe-db-mcp settingsprintsquery_timeout_seconds.safe-db-mcp settings timeoutwrites it. - Reachability. The sidebar shows Connected or Not connected for the selected connection. The Connections screen labels that connection Selected, not Active.
- MCP runtime. The bundled Temurin 25 runtime for
@safe-db/mcpisjdk-25.0.5+8.
1.1.0
The desktop app, the MCP server, and the shared query engine. The MCP server now has 20 tools.
- Catalog discovery.
search_catalogfinds tables, columns, indexes, and foreign keys without loading the whole schema.find_join_pathsshows how tables connect.describe_tablenow includes which columns can join and incoming foreign keys. - Query assessment.
assess_queryscores aSELECTagainst the risk gate without running it or writing history. Allowed queries include the same risk reasons as blocked ones. - Sample analysis. Pivot, filter, and export a fetched sample without another query. CSV exports stay on disk after the in-memory sample expires.
- Workspaces. Save, run, and delete queries; list history; apply Explore recipes. Destructive deletes wait for confirmation.
- Resources and prompts. Agents can read
safedb://connections, tables, and result summaries, and followexplore-databaseandanalyze-resultprompts. - CLI. Test saved connections, change the risk gate and blocked schemas, and import or export recipes.
- Desktop. Pivot labels use the column name, and qualify with the table when
two names collide. Each row dimension is its own column.
LIKEwithESCAPEround-trips through the Query Builder and saved queries. Duplicate risk reasons collapse to one signal. A MySQL plan that cannot be parsed no longer asks for confirmation on an otherwise allowedSELECT.
1.0.1
- History. Builder and SQL runs appear as they complete, without restarting the app. Delete a single entry, or clear the whole list.
- Light mode default. New installs start in light mode. A missing or unrecognized theme value also starts light. An explicitly saved dark theme stays dark.
- Query builder layout. The toolbar wraps the connection controls and Run as
groups at the 960x600 minimum window with the sidebar expanded. Joins stay reachable at that
size, and Query options opens a dialog with distinct rows, grouping,
sorting, and joins. Filters sit in a height-bounded scrolling strip above the canvas, so a
long
INlist cannot cover the table cards. - Filters. Filter chips stay visible at the default width with the sidebar
expanded.
BETWEENfields stay together with theirfrom,and, andtolabels, and the operator menu no longer truncatesBETWEEN. Each wrappedINvalue keeps its remove button, and timestamp values stay readable. - Table cards. Column names show at every width. A card shows column types once it is wide enough, and hovering a column name reveals the type on a narrower card. Each column toggle has an accessible label.
- SQL workspace. The header wraps the title, connection and schema pickers, and Run as groups at the 960x600 minimum. With no saved connection selected, the screen shows only the Choose a database to query prompt and an Open Connections action.
1.0.0
The desktop app, the MCP server, and the shared query engine.
- Connections. Connect timeout of about 10 seconds via driver connect, login,
and socket properties plus an interruptible deadline. Authentication failures and
unreachable hosts return the MCP
connectionerror. - MCP errors. Every tool failure returns JSON
{error, message, warnings}withisError=true. Unknown extra arguments returninvalid_arguments. - Result previews.
run_querypreviews andget_result_rowspages stop around 32 KiB. Long cells end with…[truncated].page_truncatedandnext_offsetare included when more sample rows remain. - Risk gate. Severity decides: High blocks at Standard, Very high blocks at
Flexible. PostgreSQL and MySQL cap EXPLAIN rows under LIMIT. Large join-side lookups score
High. A foreign-key check without an index is ignored when a Limit keeps examined rows in
the Low band. Disabled skips EXPLAIN. A plan-check timeout reports a short
executionerror instead of asking for confirmation.