Sequel Ace: a macOS MySQL and MariaDB client, and what it will not do for you

What Sequel Ace is, and who it is actually for

Sequel Ace describes itself as the "sequel" to Sequel Pro, the long-running macOS database tool. It is a native Mac application for working with MySQL and MariaDB databases, written primarily in Objective-C, and the README frames it as a fast, easy-to-use client rather than a general database platform. The audience is narrow and specific: developers and DBAs who work on a Mac and whose databases are MySQL or MariaDB. If either half of that sentence is false, the project is the wrong tool, and the compatibility list says so plainly. macOS must be 13.5 or later. MySQL must be 5.7 or later. MariaDB must be 10.0 or later. The README points people on older macOS versions at pinned older releases, from version 5.4.0 down to 2.3.2, with the warning that no support is provided for old versions and compatibility is not guaranteed. That is an honest boundary rather than a marketing one, and it is worth reading before you download anything. The project is not archived, and its last push was on 2026-09-21, with a 6.0.1 release candidate tagged the same day and 6.0.0 tagged on 2026-09-17.

How the app is put together, and what the MCP server adds

The repository layout is a standard Xcode project: Source/, Frameworks/, Resources/, UnitTests/, SharedSupport/, plus a sequel-ace.xcodeproj at the top level. Build and release work is split across Scripts/, fastlane/ and ci_scripts/, and there is a Gemfile for the Ruby side of that tooling. Translations run through Crowdin, which is why crowdin.yml sits in the root and why the README sends contributors to the Crowdin project rather than to in-repo translation files. The part worth attention is the MCP server. According to the README, Sequel Ace includes a built-in Model Context Protocol server that lets AI agents such as Claude Code and Cursor query your databases through Sequel Ace's existing connections. Three constraints are stated: it is off by default, it listens on localhost only, and it runs in read-only mode unless you turn that off. The README points at a separate MCP server guide on sequel-ace.com for setup, the tool list, client configuration and the security model. That is the right place for those details, but it also means the repository README alone does not tell you which tools the server exposes or how authentication works. Treat the read-only default as the useful part: it means enabling the server does not immediately grant write access to whatever connection is selected.

Installing Sequel Ace on a Mac: three routes

There are three documented install paths, and they are not equivalent. The App Store build is the one the project treats as the release channel, since production/ tags represent submissions to the macOS App Store. The mas CLI installs that same App Store build by identifier. The Homebrew route installs a cask that the README explicitly calls unofficial and community maintained, built from the GitHub release rather than from the App Store. If you are scripting a machine setup, mas is the closer match to the supported channel. The command below installs Sequel Ace by its App Store identifier; the comment is the project's own.

mas install 1518036000 # Sequel Ace

If you prefer Homebrew, the README gives this cask command. Note again that this is the community cask, not an official distribution channel.

brew install --cask sequel-ace

For a first real use, the migration path matters more than a blank connection. The README links a migration guide for moving saved connections from Sequel Pro, which is where most people arriving at this project are coming from. After that, connections are stored as favourites in the app. The MCP server, if you want it, is not configured in a file: the README says to enable it under Preferences > MCP Server, and then follow the separate guide for client configuration.

Where Sequel Ace stops: platform, engine and licence boundaries

The clearest limitation is the platform. Sequel Ace is a macOS application, and the README's compatibility section lists only macOS, Intel and Apple Silicon. There is no Windows build, no Linux build and no documented self-hosted or Docker deployment. People search for a Sequel Ace Ubuntu or Windows version; the README offers nothing for either, and the honest answer is that those builds do not exist. The second boundary is the engine. The README names MySQL and MariaDB and nothing else, so PostgreSQL and SQLite are out of scope. The third is the licence situation. The README states that Sequel Ace is free and open-source software licensed under MIT, with copyright held by Moballo, LLC, and forked from Sequel Pro. The repository metadata, however, reports the licence as NOASSERTION rather than MIT. Those two statements do not agree, and anyone who needs a clean licence answer should read the LICENSE file itself rather than the README summary. That is not a legal opinion, just an observation about what the two sources say. Finally, there is a support boundary in the README worth repeating: the pinned older releases exist, but no support is provided for them and compatibility is not guaranteed.

Sequel Ace vs DBeaver, and the alternatives for other engines

The comparison people actually search for is Sequel Ace vs DBeaver, and the difference is scope. Sequel Ace is a single-platform, two-engine client: macOS only, MySQL and MariaDB only. DBeaver is the opposite bet, a cross-platform client that covers many database engines. If you need one tool for PostgreSQL, SQLite and MySQL across Mac, Windows and Linux, Sequel Ace is not that tool, and the README does not pretend otherwise. The trade-off runs the other way too. A client that targets one platform and two engines can lean on native macOS behaviour, which is what the Objective-C codebase and the App Store distribution imply. Against Sequel Pro, the difference is maintenance rather than approach: Sequel Ace is the fork that is still receiving releases, with 6.0.0 shipped on 2026-09-17, while the README treats Sequel Pro as the ancestor you migrate saved connections away from. If your constraint is a database engine or an operating system rather than a preference for a native Mac UI, the alternative is whichever cross-platform client covers that engine, not a different build of Sequel Ace.

Maintenance, releases and the upgrade cost you should expect

The release cadence is visible in the tags. The README explains the two prefixes: production/ tags are submissions to the macOS App Store and are marked as Pre-Release until Apple approves them, and both release candidates and final releases use production/ tags, with RC or Release Candidate in the title. beta/ tags are pre-release builds for testing new features and fixes, and the beta app has a different name and identifier (Sequel Ace Beta) so it can be installed side by side with the App Store release. Beta builds also have increased logging turned on. That side-by-side property is the practical upgrade story: you can run a beta next to your stable install without replacing it. The cost is that beta logging is noisier by design, so it is not the build to hand to someone who just needs to run queries. On the stable side, the App Store channel means upgrades wait on Apple review, which is a real delay between a production/ tag appearing and the update reaching users. Recent tags show 6.0.1 as a release candidate on 2026-09-21 and 6.0.0 as a full release on 2026-09-17.

Contributing, translations and where the project asks for help

The README routes contributors through a Contributing guide and a separate developer guide in the Guides/ directory, and points at the projects page and labelled issues for work that needs doing. The labels named are Help Wanted, Bug, Feature Request and PR Welcome. Translations are handled entirely on Crowdin, and the README asks anyone wanting a new language to open an issue so the maintainers can enable it. All contribution pull requests go to main, which the README calls the active development branch. There is a Code of Conduct in Guides/ and a SECURITY.md at the root, so security reports have a stated destination rather than going through the public issue tracker. The repository also carries an AGENTS.md and a .mcp.json at the top level, which lines up with the built-in MCP server described in the README. For someone evaluating the project rather than contributing to it, the useful signal here is that the contribution path is documented and the translation workflow is external, which means a missing translation is a Crowdin gap rather than a code gap.

Editorial conclusion

Adopt Sequel Ace if your work is MySQL or MariaDB on macOS 13.5 or later and you want a native client with saved connections, and consider it if you want an AI agent to query those databases through the built-in MCP server. Do not adopt it for PostgreSQL, SQLite, Windows or Linux; those are outside what the README claims, and the alternative-for-those-platforms searches are answered by other tools, not by Sequel Ace. Before committing, verify three things: your macOS and database versions against the compatibility list, that the Homebrew cask is acceptable given it is community maintained and unofficial, and that the MIT licence in the repository matches what your legal review expects, since the repository metadata reports the licence as NOASSERTION.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. Sequel-Ace/Sequel-Ace on GitHub