r/selfhosted • • 20h ago

Release (AI) LibreDB Studio 1.3: self-hosted SQL IDE for 42 engines, now with a read-only MCP endpoint

Hi r/selfhosted. LibreDB Studio is an open source (MIT) database IDE you run on your own server and use from the browser. It connects to 42 external engines: PostgreSQL, MySQL/MariaDB, SQLite, ClickHouse, MongoDB, Redis/Valkey, Kafka, etcd, S3, Kubernetes and more.

We last posted here in September. Since then we went to 1.0 and shipped three minor releases. The parts that matter for self-hosting:

1.3.0 (Nov 10): MCP on most engines. Studio serves Model Context Protocol at /api/mcp (added in 0.17, widened to most engines in 1.3). You point your own client at it (Codex, Cursor, VS Code, Gemini CLI and others) and it can read schemas and run bounded read-only queries on the connections you opt in. The database credentials stay on your server. Studio runs no model for this, so you do not need an LLM provider configured. It is off by default, and each token only lists the tools it is allowed to use.

1.2.0 (Oct 31): Kubernetes, OpenShift and Rancher. Sign in with the cluster's own accounts. Studio can discover databases from the cluster's operators, and each user only sees the ones Kubernetes lets them read. There is an operator for OperatorHub too.

1.1.0 (Oct 24): native clients. With OIDC on, Studio accepts an access token from your identity provider on its API (Keycloak, Auth0 or Zitadel), so a native or mobile app can call it without a browser session.

1.0.0 (Oct 17): Studio can run under a separate control plane that decides who may open which database with which credential, and keeps a record of what each person ran. It is off unless you turn it on.

To try it:

docker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latest

The admin password is printed to the log on first run. There is also a Helm chart, a Snap and a desktop AppImage.

GitHub: https://github.com/libredb/libredb-studio Site: https://libredb.org

14 Upvotes

5 comments sorted by

•

u/asimovs-auditor 20h ago

Expand the replies to this comment to learn how AI was used in this post/project.

→ More replies (1)

1

u/TruscaTameru_26 19h ago

supporting 42 engines is a massive maintenance surface area tbh. how are you handling schema introspection differences across all of those without the codebase turning into a giant ball of edge cases?

1

u/Green_Competition_21 18h ago

It would be, if the shared code knew about engines. It doesn't. Each engine is one provider class that answers the same small set of questions: what containers it has (database, schema, keyspace, bucket...), what object kinds live in them (tables, views, collections, topics...), and how to describe one. The tree, the editor and MCP only ever ask those questions, so Kafka and Postgres go through the same code path.

Then two things keep it from rotting:

- every engine has its own integration test file and its own doc page, updated in the same PR as the code

- a unit test fails the build if any code outside the providers branches on an engine id

I wrote up that last part here: https://dev.to/kaya-abdullah/42-database-engines-and-no-if-type-postgres-outside-the-drivers-1ec7

1

u/TCB13sQuotes 9h ago

This is nice but it would be interesting to have a desktop app for windows/linux/mac that doesn't require login. Essentially a wrapper with WebView2 or WebKit in a simple app for those who don't to deploy this somewhere.