Database Explorer

A local database explorer for backend evidence

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

The current database workspace supports saved connections and active drivers for SQLite, PostgreSQL, and MySQL-compatible databases.

SQLite, PostgreSQL, and MySQL

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

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

Run a current statement, selection, or multi-statement batch and inspect each result in the query workspace.

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. API symptom
→
2. Server evidence
→
3. Database state
→
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

API Client

Capture the request and response that exposed the data problem.

Explore API Client

SSH Terminal

Inspect logs and runtime state before changing persisted data.

Explore SSH Terminal

MCP Integration

Let an AI agent gather database evidence through approved tools.

Explore MCP Integration

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