Sequa.AI vs turbocharge
Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). turbocharge is a plugin bundle for AI coding tools published by aguerlain-lr. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Sequa.AI | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f4e0e271c5c5 Forks (GitHub): 5 Pulls (Docker Hub): 10 290 Stars (Docker Hub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Sequa.AI | turbocharge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 22 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 10 290 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sequa) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/sequa-ai/sequa-mcp | github.com/aguerlain-lr/turbocharge |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Sequa.AI
Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.
turbocharge
You found a plugin that makes your coding agent actually good. One thing bothers you. So you fork it and change it. Three weeks later, upstream ships a release with fixes you want. Now you have a choice: manually hunt through the diff to reapply your changes, or leave your fork to rot. Turbocharge is a set of three skills that manage this cycle for you. Fork freely. Customize intentionally. Sync automatically.
How to run each
Sequa.AI As a local MCP server: Docker image
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequaRequires: API_KEY (secret)
turbocharge
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of turbocharge publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of turbocharge publish no settings it asks for, so we do not compare settings.
What it can do: Sequa.AI · What it can do: turbocharge · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.