Open-source project
Sequel-Ace/Sequel-Ace avatar
Sequel-Ace/Sequel-Ace

Sequel Ace lists four old builds and an MCP server that is off by default

MySQL/MariaDB database management for macOS

7,563 stars341 forksObjective-CNOASSERTION

At a glance

What is it?
An MIT licensed MySQL and MariaDB client for macOS, descended from a tool that shipped in 2002, with two tag namespaces because one of them is really an App Store submission channel. The newest feature is a Model Context Protocol server that is disabled by default, bound to loopback and read-only unless you say otherwise.
Who is it for?
Sequel Ace fits a macOS developer who wants a native database client with saved connections migrating from an older tool, and who wants an agent to query their databases without handing over write access. It does not fit anyone on Linux or Windows, since the readme lists macOS as the only platform.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Objective-C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Sequel-Ace/Sequel-Ace7,563 ★ · +28
Star history
Repository2026-09-222026-11-15
Sequel-Ace/Sequel-Ace7.5k7.6k

28 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Six older builds, pinned to macOS ranges

The previous versions section is a list of five entries, and it carries a disclaimer that is worth reading before anything else: no support is provided for old versions, compatibility is not guaranteed, and you use them at your own risk.

The current build needs a recent macOS, a supported processor generation, and a supported database server. Below that, four earlier builds are mapped to operating system ranges: one for the two most recent unsupported macOS versions, one for two older ranges, one for very old systems or an old database server, and one for the oldest supported pair.

One row maps two separate operating system ranges to the same build, and it carries an extra requirement: on the older of those two, you must install Apple's Swift standard libraries separately, from either the project's own scripts directory or from Apple.

That last detail is the clearest illustration of what this section is for. On Mac OS X 10.13-10.14.4 the old build will not work as expected without something installed by hand, and the readme would rather say so than let you discover it.

The MCP server is off, loopback only, and read-only

The newest feature in the readme is an agent integration, and its security posture is stated in three clauses in one paragraph.

Sequel Ace includes a built-in Model Context Protocol server that lets agents, with two named clients, query your databases through connections the application already has. It is off by default. It listens on localhost only. And it runs in a read-only mode unless you turn that off.

Three defaults, each narrowing the blast radius.

The agent works through Sequel Ace's existing connections rather than its own. That is also the risk. An agent with write access to every connection in your saved list is not a narrow capability, so the toggle is the thing to think about rather than the feature.

Configuration is one menu deep, under preferences, and the readme links a guide with the tool list, client configuration and the security model.

Two tag namespaces, and only one is an app you can run

The repository uses two kinds of tag and the readme explains what each one means, which is unusual and useful.

One namespace represents submissions to the Mac App Store. Those tags are marked as pre-release until Apple approves them and the team officially releases them, and both release candidates and final releases use that same namespace, with candidates marked in the title.

The other namespace holds pre-release builds intended for testing new features and fixes. And those builds have a different name and a different application identifier, so you can install one alongside the store version.

Increased logging is enabled in those testing builds as well, which tells you what to expect if you run one: more output than the shipping app.

So the tag list mixes two different things, a submission pipeline and a testing channel, and the naming is the only way to tell them apart. Release candidates carry RC or Release Candidate in their title, and production/ tags stay pre-release until Apple approves them, so the newest tag is not necessarily what users have.

Three install routes and one of them is unofficial

Installation has three paths and the readme is precise about which is which.

The official route is the Mac App Store.

The store route also has a command line form, which takes the numeric application identifier and needs the store command line tool installed first:

sh
mas install 1518036000 # Sequel Ace

The third route is a Homebrew cask, and the wording is careful: it is an unofficial, community-maintained cask of the project's own GitHub release, not an official formula.

That distinction matters because a cask installed from a GitHub release is a build that did not come through the store, so it updates on the release cadence rather than the review cadence, and it is maintained by someone other than the team.

The copyright line goes back to 2002

The licence section is four lines and they tell a twenty-four year old story.

The current copyright is held by a limited liability company and runs from 2020 to the present. Below it, a line records that the project is forked from a different tool, and that tool's copyright runs from 2002 to 2019 and is held by two teams, one of them the original MySQL Cocoa-era team.

Then the actual terms: free and open-source software under the MIT licence.

The repository metadata, meanwhile, reports no recognised licence, which is the kind of mismatch that makes a licence scanner unhappy and that the files in the repository settle.

For a project whose entire value is being the maintained continuation of a tool people have used for two decades, keeping that lineage in the licence file is not decoration.

Releases are submissions, so a candidate can precede a release

The release sequence in the repository shows the submission pipeline working.

Patch 6.0.2 went out on 2026-10-04 and 6.0.3 followed four days later. The newest tag, 6.1.0 (20117), was published on 2026-10-23.

Its title does not mark it as a candidate, but production/ tags stay marked pre-release until Apple approves them.

That is the correct consequence of routing releases through a store: the version number exists in the repository before a human at the platform has approved the binary. Anyone scripting an install from the newest tag will get something the store has not approved, which is fine for testing and wrong for a fleet.

The readme's guidance is to treat those tags as pre-release until the team says otherwise, which is the rule to follow.

Translations live on Crowdin, and a new language needs an issue

Localisation is run through a translation platform rather than through pull requests, and the process has two halves.

To translate an existing language you sign up for the platform and join the project. To add a language that does not exist yet, you open an issue first, and the maintainers will enable it.

That second step is the one to note, because adding a language to a translation platform is not a pull request and the readme is explicit that it starts with an issue.

For development work, the same shape applies. The readme sends you to the project board and to issues carrying four specific labels, and describes the mix of difficulty there, noting that new contributors should be able to find something straightforward to start on.

The contribution rule itself is one line and unambiguous: every pull request should be pointed at the branch the project designates for development, which it names.

Ruby tooling releases an Objective-C application

The repository root explains the toolchain without opening a project file.

There is an Xcode project, and the sources are split into a source directory, a shared support directory, a resources directory and an entitlements directory. There is also a frameworks directory, which is where vendored dependencies live in an application of this kind, and unit tests beside them.

And then there is Ruby: a gem file with a lockfile, a fastlane directory, continuous integration scripts, and an artwork directory.

The Ruby half is release automation. Building a signed application bundle, uploading it, managing the store submission and the metadata that goes with it is done with a tool written in Ruby, which is why a native Mac application ships with a gem file in its root.

There is also a configuration file for an agent client at the root and one for a static analyser, plus a security policy at the root and a code of conduct and contributor guide under a guides directory.

Editorial conclusion

Sequel Ace fits a macOS developer who wants a native database client with saved connections migrating from an older tool, and who wants an agent to query their databases without handing over write access. It does not fit anyone on Linux or Windows, since the readme lists macOS as the only platform. Before upgrading from a previous build, check the compatibility table rather than the latest tag, and if you enable the MCP server, understand that turning off read-only mode gives an agent write access to every saved connection.

Frequently asked questions

What is Sequel Ace?

It is a MySQL and MariaDB database management application for macOS, MIT licensed and described as the sequel to the longtime Mac tool Sequel Pro. The current release requires macOS 13.5 or newer, supports both Intel and Apple Silicon, and works with MySQL 5.7 or newer and MariaDB 10.0 or newer.

How do I install Sequel Ace on a Mac?

Download it from the Mac App Store, or use the store command line tool with the numeric application identifier. There is also a Homebrew cask, which the readme describes as unofficial and community maintained, built from the project's GitHub release rather than from the store.

What are the differences between Sequel Pro and Sequel Ace?

Sequel Ace is a fork of Sequel Pro, whose copyright runs from 2002 to 2019 and is held by the Sequel Pro and CocoaMySQL teams, with the current copyright held by a company from 2020 onward. Saved connections can be migrated from the older tool using a migration guide, and earlier macOS versions are matched to specific earlier Sequel Ace builds.

Is Sequel Ace free?

It is free and open-source software under the MIT licence, and the readme also asks for sponsorship through an open collective platform or through GitHub Sponsors for the maintainers. There is no paid edition mentioned anywhere in the readme.

Can an AI agent query my databases with Sequel Ace?

Yes, through a built-in Model Context Protocol server that works with the connections the application already has, with two named clients supported. It is off by default, listens on localhost only, and runs in read-only mode unless you turn that off, and you enable it under the preferences menu.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. Sequel-Ace/Sequel-Ace on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sequel-ace-sequel-ace.svg)](https://hysenlabs.com/projects/sequel-ace-sequel-ace)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sequel-ace-sequel-ace.svg)](https://hysenlabs.com/projects/sequel-ace-sequel-ace)

Was this useful?