Skip to main content
Glama
platypus-db

platypus-db

Official
README.md
<h1 align="center">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="docs/brand/platypus-db-on-dark.png" />
    <img src="docs/brand/platypus-db-on-light.png" alt="PlatypusDB" width="640" />
  </picture>
</h1>

<p align="center">
  <strong>A fast, small SQL client for people who work with many databases.</strong>
</p>

<p align="center">
  <a href="https://github.com/platypus-labs/platypus-db/releases/latest"><img src="https://img.shields.io/github/v/release/platypus-labs/platypus-db" alt="Latest release" /></a>
  <a href="https://github.com/platypus-labs/platypus-db/releases"><img src="https://img.shields.io/github/downloads/platypus-labs/platypus-db/total" alt="Downloads" /></a>
  <a href="LICENSE"><img src="https://img.shields.io/badge/license-AGPL--3.0--or--later-blue" alt="License: AGPL-3.0-or-later" /></a>
  <img src="https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-lightgrey" alt="Platforms: Windows, macOS, Linux" />
</p>

<p align="center">
  <b>English</b> · <a href="README.it.md">Italiano</a>
</p>

PlatypusDB™ is a desktop SQL client for developers, DBAs and analysts who work with several
databases in a day. One small app runs queries, browses and edits data, designs tables,
explains slow statements and documents schemas, and keeps production connections clearly apart
from the others. A Rust core with a Tauri 2 + React interface: an installer of about 20 MB, a
window ready in under a second, and a results grid that scrolls through millions of rows.

![A million rows opened from the navigator, scrolled and sorted from the header](docs/screenshots/hero.gif)

## Why PlatypusDB

- **Light.** A 20 MB installer on Windows and a 30 MB download on Linux, against 122 MB for
  DBeaver, 346 MB for Beekeeper Studio and about 1 GB for DataGrip; a window in under a second.
- **Safe with production.** Connection types color the window frame, risky statements ask
  first, production opens in manual commit, and every save of edited rows leaves an undo script.
- **Many databases, one app.** PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, ClickHouse,
  SQLite, DuckDB, MongoDB, Redis, Elasticsearch, Cassandra, Snowflake, BigQuery and more, with the same editor and grid.
- **Ready for agents.** Claude Code, Codex, Cursor and other MCP clients use your saved
  connections with the access you give each one, and their changes wait for your OK.
- **Open source.** AGPL-3.0, no account, no telemetry.

## Install

Download the installer for your system from the
[releases page](https://github.com/platypus-labs/platypus-db/releases/latest): `.exe`/`.msi` for
Windows, `.dmg` for macOS, `.AppImage`/`.deb`/`.rpm` for Linux. The app updates itself.

1. Open PlatypusDB and click **New connection**, or paste a connection URL
   (`postgres://…`, `mysql://…`, a JDBC URL or an ADO.NET string).
2. No database at hand? **Try the sample database** on the welcome screen: a SQLite field
   survey of platypuses, with linked tables, a view and saved scripts.
3. Press `Ctrl+K` for the command palette: every action, connection and table is a few letters
   away.

**Portable copy**: put the executable in a folder with an empty `data` folder beside it.
Connections, settings, history and scripts then live in `data`, and the folder can move to
another machine or a USB stick ([more](docs/user/FEATURES.md#portable-copy)).

The [user guide](docs/user/guide/README.md) goes on from here, task by task: [getting
started](docs/user/guide/getting-started.md), connecting, queries, safety, troubleshooting.

## Databases

PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, ClickHouse, SQLite, DuckDB, libSQL, MongoDB,
Redis, Elasticsearch, Cassandra, Snowflake, BigQuery, Databricks, Trino, IBM Db2, ODBC and the
databases that speak the PostgreSQL protocol. How each one connects, its oldest supported
version and what works on it are in the [databases guide](docs/user/guide/databases/README.md).

## Features

| Write SQL | Edit data safely |
|---|---|
| ![A JOIN completed from the foreign key, run and drawn as a chart](docs/screenshots/editor.gif) | ![Cells changed and a row added, the SQL previewed, then saved](docs/screenshots/data-editor.gif) |
| **Find slow steps** | **Browse the data** |
| ![Explain analyze with the heatmap and an index suggestion](docs/screenshots/explain.gif) | ![The data viewer sorted from its header, with the value panel](docs/screenshots/data-viewer.png) |
| **Design tables** | **Find anything** |
| ![Designing a table](docs/screenshots/table-editor.png) | ![The command palette](docs/screenshots/palette.png) |

Connections over SSH, proxies and cloud sign-in; a SQL editor with completion; a data viewer and
editor; charts and notebooks; table design, ER diagrams and schema comparison; query plans;
server activity; import, export and transfer; projects and seven languages. Every feature, area
by area: **[docs/user/FEATURES.md](docs/user/FEATURES.md)**. Task by task: the
[user guide](docs/user/guide/README.md). Keyboard shortcuts: [docs/user/SHORTCUTS.md](docs/user/SHORTCUTS.md).

## Agents (MCP) and the CLI

Claude Code, Codex, Cursor and other MCP clients can use your saved connections, with the access
you give each one: none, read only (the default) or read and write. A change an agent wants to
run opens a dialog in the app first. Setup, tools, limits and the `platypus` CLI:
[docs/user/AGENTS.md](docs/user/AGENTS.md).

## Performance

PlatypusDB 0.6.0 on Windows 11 (Ryzen 7 9700X, 32 GB):

| | PlatypusDB 0.6.0 |
|---|---|
| Start, until the window has finished drawing | 0.7 s (0.8 s the first time) |
| Memory at rest, the app and its web view | 170 MB |
| A million rows from SQLite | first page in 0.3 s, the rest 0.3 s later; the window never stalls |
| Windows installer | 20 MiB |

Next to DBeaver on the same machine, both started five times without a connection, DBeaver on a
profile already set up:

| | PlatypusDB 0.6.1 | DBeaver CE 26.2.3 |
|---|---|---|
| Start, until the window has finished drawing | 0.7 s | 5.2 s |
| Memory at rest | 170 MB | 488 MB |

Next to other SQL clients, by the size of their official Linux downloads:

| | PlatypusDB 0.6.0 | DBeaver CE 26.2.3 | DataGrip 2026.2.6 | TablePlus 2.2.0 | Beekeeper Studio 6.2.0 |
|---|---|---|---|---|---|
| Runtime | Rust and the system's web view | Java, JRE bundled | Java, JetBrains Runtime bundled | Native (GTK) | Electron |
| Download | 30 MiB (`.deb`) | 122 MiB | 1,047 MiB | 60 MiB | 346 MiB |
| On disk | 68 MiB, plus the system's WebKitGTK | 206 MiB | not published | 180 MiB | 1,105 MiB |
| License | AGPL-3.0 | Apache 2.0 | Proprietary | Proprietary | GPLv3 |

How each number is taken, the scale tests and the Linux measurements: [docs/dev/BENCHMARKS.md](docs/dev/BENCHMARKS.md).

## Development

Build, test, project layout and the dev databases: [docs/dev/DEVELOPMENT.md](docs/dev/DEVELOPMENT.md).
What comes next is in [docs/dev/ROADMAP.md](docs/dev/ROADMAP.md) (in Italian); every document is listed in
[docs/README.md](docs/README.md), and the changes of each release in
[CHANGELOG.md](CHANGELOG.md).

## Contributing

Bug reports, ideas and pull requests are welcome: open an
[issue](https://github.com/platypus-labs/platypus-db/issues) first for anything larger than a small
fix. [CONTRIBUTING.md](CONTRIBUTING.md) explains how to build, test and submit a change. Everyone
taking part follows the [Code of Conduct](CODE_OF_CONDUCT.md).

## Security

Please report vulnerabilities privately, not in a public issue: see [SECURITY.md](SECURITY.md).

## License

PlatypusDB is licensed under the [GNU Affero General Public License v3.0 or later](LICENSE)
(AGPL-3.0-or-later). You can use, study, change and share it freely; if you distribute it, or
run a changed version as a service for others, you must release your source code under the
same license. Third-party code and assets keep their own licenses:
see [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

The name and the logo are not part of that license. PlatypusDB™ and the PlatypusDB logo are
trademarks of the PlatypusDB maintainers: as AGPL section 7(e) allows, no rights are granted
under trademark law, and the logo and icon files listed in [NOTICE](NOTICE) are © 2026
PlatypusDB maintainers, all rights reserved. You can name the project, link to it and
redistribute the official builds unchanged; a fork must ship under its own name and icons. The
details are in [TRADEMARKS.md](TRADEMARKS.md).

TDQS

A3.9/5.0

Scored across 24 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions, and the descriptions draw sharp boundaries between similar-sounding tools such as explain vs. estimate_change and run_query vs. sample_rows. A few pairs still require careful reading, but an agent can generally select correctly.

Naming Consistency4/5

The set is overwhelmingly snake_case with a verb_noun pattern (list_objects, describe_table, propose_sql, search_history). Minor deviations like top_queries, next_page, server_activity, and explain are readable but break the pattern slightly.

Tool Count3/5

At 24 tools, the surface is heavy for a database MCP server and sits at the upper end of the borderline range. Each tool appears purposeful, but the breadth of schema, query, admin, scripting, and proposal features makes the set large enough to feel burdensome.

Completeness5/5

The tool set covers connection discovery, schema and object introspection, querying, pagination, explain/estimate, profiling, sampling, cross-database queries, SQL and row-edit proposals, scripts, history, sessions, server activity, and schema comparison. No obvious lifecycle or workflow gap remains for the stated database-assistant purpose.

Maintenance

ActivityNo data
ResponsivenessOutdated data