Gridex puts seven database drivers behind one adapter protocol and an MCP server
A native macOS / windows / Linux database IDE built with Swift and AppKit. Connect to PostgreSQL, MySQL, SQLite, and Redis from a single app with a fast, keyboard-driven interface.
At a glance
- What is it?
- Gridex is a native database IDE written in Swift with AppKit, WinUI 3 and Qt 6 front ends, where the engineering decision that matters is a roughly fifty-method DatabaseAdapter protocol, and the product decision that matters is exposing a saved connection to an AI agent through thirteen or fifteen permission-tiered MCP tools.
- Who is it for?
- Adopt Gridex if you move between several database engines daily and want one native window with the same grid, editor, ER diagram and backup behaviour everywhere, and if you want to expose a read-only connection to an AI client rather than scripting your own bridge.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
Three native front ends, one binary per platform
Gridex ships as three platform builds rather than one cross-platform runtime. On macOS it is a universal DMG covering Apple Silicon and Intel, signed and notarized, with auto-update through Sparkle. On Windows it is a Velopack installer for Windows 10 and 11. On Linux it is an x86_64 AppImage built against Qt 6, with self-update from a JSON feed.
The UI stack follows the platform rather than being wrapped: AppKit on macOS, WinUI 3 on Windows and Qt 6 on Linux, and the README is explicit that there is no Electron and no web view behind the data grid. The language is Swift, with a Swift 5.10 badge, and the repository has a Package.swift at the root plus per-platform directories named macos/, windows/ and linux/ and a dev.sh.
System floors are stated in the badges: macOS 14 or later and Windows 10 or later, with Swift 5.10 as the language level.
For a specific version, delta updates or checksums, the README sends you to the GitHub releases page and to the download page on the project's own site rather than to the three always-latest links, which is the honest distinction between the convenient path and the reproducible one.
The adapter protocol is what makes seven engines behave the same
The claim that carries the architecture is that all drivers share the same DatabaseAdapter protocol, roughly fifty methods, so every feature works identically across engines: the grid, the query editor, the ER diagram, backup and MCP.
That is a much stronger promise than a multi-database client that merely opens connections. A fifty-method protocol is a large surface, and every feature that touches data has to be implemented per engine or emulated. The reward is that learning Gridex once transfers across seven databases.
The drivers are named individually rather than being described generically. PostgreSQL uses PostgresNIO with parameterized queries, mTLS, sequences and full schema inspection. MySQL uses MySQLNIO with charset handling, parameterized queries, TLS and auto-reconnect with keepalive. SQLite uses the system libsqlite3 with file-based storage, WAL mode and no configuration. Redis uses RediStack with a key browser, SCAN filter, Server INFO dashboard, Slow Log viewer and rediss:// TLS. MongoDB uses MongoKitten with a document editor, NDJSON backup and restore and the aggregation pipeline. SQL Server uses CosmoSQLClient with TDS 7.4 and no FreeTDS dependency, native BACKUP DATABASE and stored procedures. ClickHouse is pure Swift over URLSession HTTP on ports 8123 and 8443, with full mTLS via PKCS#12, system.* introspection and version-aware fallbacks from CH 20.8 onwards.
Those are the primitives each engine actually has, and the README's point is that a tool that assumes SQL everywhere will be wrong somewhere on that list.
Seven drivers on macOS, six everywhere else
Platform coverage of drivers is uneven and the README says so.
The headline is seven drivers in one native binary, then the detail: seven drivers on macOS, six on Linux and Windows, with ClickHouse macOS-only for now. The download matrix confirms the same split, listing MongoDB, SQL Server and ClickHouse among the supported databases.
That is the kind of gap that only shows up when you need it. If your estate includes SQL Server or MongoDB you are covered on all three platforms. If it includes ClickHouse, your team is on macOS or the team uses another client for that engine.
The same asymmetry appears in the MCP server, which is available on macOS over stdio, on Windows over stdio and HTTP, and on Linux over stdio. So the HTTP transport for an MCP client is a Windows-only convenience, and anyone writing a cross-platform agent setup should plan for stdio everywhere.
The MCP server is a permission model, not a bridge
Gridex can expose a saved connection to Claude Desktop, Cursor or any MCP client, and the interesting part is what guards the tools.
The tool surface is organised into permission tiers. Schema tier tools include list_connections, list_schemas, list_tables, describe_table, list_relationships and get_sample_rows, and are always allowed for enabled connections. Read tier tools are query, explain_query and search_across_tables, allowed in read_only and above modes, with a SQL sanitizer that rejects write statements. Write tier tools are insert_rows, update_rows, delete_rows and execute_write_query, which require read_write mode, are gated by a row-count estimator that flags bulk changes, and require user approval. DDL and Advanced tiers are described as future tools for schema migration and administration, requiring read_write plus explicit user approval.
Every tool call runs through a permission gate and is recorded in an audit log, per the README.
One inconsistency is worth flagging because it affects how you read the feature. Two passages give different counts for the same thing: the feature list says 13 tools with a 3-tier permission model and an audit trail, while the MCP section says 15 tools across 5 permission tiers. The table that follows lists four populated tiers and two future ones, which matches the second number. Treat the counts as unsettled rather than picking one.
Credentials in the OS keychain, no telemetry, no proxy
The privacy claim is specific and checkable.
Credentials stay local: macOS Keychain on macOS and Windows Credential Manager on Windows. There is no cloud sync, no telemetry and no proxy.
For a tool that connects to production databases, that is the property most worth verifying yourself rather than taking on trust. A database client with an embedded AI feature and a built-in agent bridge is exactly the shape of software where a default changes from local to remote without appearing in a changelog, so the claim is important rather than reassuring.
The AI side names the models rather than integrating one: Claude, GPT, Gemini and Ollama. Ollama being in that list means there is a fully local path, and the models can read your tables, run read-only queries and write SQL scoped to the connection you pick. That last constraint is what makes the AI feature defensible: a prompt cannot reach a database you have not explicitly connected.
Version numbering that has already moved backwards
The release history is short and irregular.
Recent tags are v0.0.19 from 2026-05-23, v0.1.12 from 2026-05-07 and v0.0.18 from 2026-05-05. The v0.0.19 tag is newer in date and lower in version than v0.1.12, which means either the project renumbered or the 0.1 line was abandoned. Either way, you cannot infer recency from the version number here, and the release filenames in the download links show the same inconsistency, with a macOS build named Gridex-0.0.11-universal.dmg and a Windows build named Gridex-stable-Setup.exe.
The repository is not archived and the last push was on 2026-09-07, so work continued after the newest tag. CHANGELOG.md is at the root and is where a version question should be answered.
Licensing is Apache-2.0, with both LICENSE and NOTICE files present, so there is no attribution or copyleft constraint on your use. Around it sits the usual set of governance files: CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, CLAUDE.md, a .claude/ directory, .github/, scripts/ and assets/.
Editorial conclusion
Adopt Gridex if you move between several database engines daily and want one native window with the same grid, editor, ER diagram and backup behaviour everywhere, and if you want to expose a read-only connection to an AI client rather than scripting your own bridge. Do not adopt it as a team database console with an audit trail you can rely on: the credential storage is the operating system's own keychain, the audit log belongs to an app with a Discord server rather than an identity system, and the release line is pre-1.0 at v0.0.19 with a version ordering that has gone backwards from v0.1.12. Verify first that your platform has all the drivers you need, since ClickHouse is macOS-only for now and Linux and Windows carry six of the seven, and that the permission tiers behave as you expect before pointing an agent at production.
Frequently asked questions
How do I install Gridex?
Download a prebuilt package rather than building it: a universal signed and notarized DMG for macOS 14 or later, a Velopack installer for Windows 10 and 11, or an x86_64 AppImage for Linux. For a specific version, delta updates or checksums, use the GitHub releases page or the download page on gridex.app.
Which databases does Gridex support?
PostgreSQL, MySQL, SQLite, Redis, MongoDB, SQL Server and ClickHouse, all behind a shared DatabaseAdapter protocol of roughly fifty methods. There are seven drivers on macOS and six on Linux and Windows, with ClickHouse macOS-only for now.
Does Gridex have an MCP server?
Yes. It can expose a saved connection to Claude Desktop, Cursor or any MCP client, available on macOS over stdio, on Windows over stdio and HTTP, and on Linux over stdio. Tools are organised into permission tiers and every call passes a permission gate and is recorded in an audit log.
Where does Gridex store database credentials?
Locally, in the macOS Keychain on macOS and Windows Credential Manager on Windows. The README states there is no cloud sync, no telemetry and no proxy.
What licence is Gridex released under?
Apache-2.0, with a LICENSE and a NOTICE file in the repository root. The platform builds require macOS 14 or later, Windows 10 or later, and Swift 5.10 as the language level.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gridex-gridex)Was this useful?