Unfour
Sign in 中文
All features

Database Explorer

A local database client for backend investigation

Unfour includes a local database explorer for inspecting schemas and data, editing supported records, and running SQL as part of backend troubleshooting.

It is built for developers who need to verify database state behind an API symptom or server-side error without moving the investigation into a separate database tool.

Read the docs

Inspect schemas, data, and query results

Use SQLite, PostgreSQL, and MySQL or compatible MariaDB servers. openGauss uses PostgreSQL-protocol connections, with table exports and consistent SQL execution context.

SQLite, PostgreSQL, and MySQL

Create and test saved connections for SQLite, PostgreSQL, and MySQL or compatible MariaDB servers.

openGauss

Connect through the openGauss preset using the PostgreSQL protocol, with server detection, catalog and table browsing, index metadata, and native table DDL improvements.

Table structure and data export

Export one table’s structure as SQL, its data as SQL, CSV, or JSON, or both as SQL. This is table export, not a whole-database backup.

SQL and Saved SQL context

Keep the selected database and schema when opening queries, running scripts, reopening history, or restoring Saved SQL. Saved queries are grouped under their database.

Schema and table browsing

Browse catalogs, schemas, tables, columns, keys, indexes, and other available structure details.

Data inspection

Open supported tables, page through rows, and use server-backed filtering and sorting.

Supported row editing

Stage and apply supported insert, update, and delete changes with review before execution.

SQL execution

Use Run All for the full editor script or Run Selected for highlighted SQL, then inspect each statement result. Whole-script checks run first and execution stops at the first error.

MCP-assisted database inspection

Expose saved connections, schema reads, read-only queries, explain output, and policy-controlled execution to MCP clients.

Evidence chain

Verify the state behind the symptom

Move from a visible API problem through server evidence to the persisted state that confirms or challenges the working theory.

  1. 1. API symptom
  2. 2. Server evidence
  3. 3. Database state
  4. 4. Developer decision

Database boundary

SQL remains visible, scoped, and deliberate

Unfour does not claim support for every database engine, autonomous schema changes, or automatically safe production SQL.

Saved database credentials remain local by default.

Supported writes are reviewed and explicitly initiated.

Mutating or high-risk MCP actions are controlled by workspace policy and confirmation checks.

The developer remains responsible for the target environment and the SQL that runs.

Related features

Keep database evidence connected to the API and server context

Download Unfour to inspect supported databases in the local workspace.

Download Unfour Read the docs View all features