Sequa.AI vs i18n-extractor
i18n-extractor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). i18n-extractor is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, 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 399 Stars (Docker Hub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | i18n-extractorno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 22 | 3 |
| Pulls (Docker Hub) (differs) | 10 399 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sequa) | On your machine (@barnburner121/plugin-hub-mcp) |
| 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 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/sequa-ai/sequa-mcp | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of i18n-extractor
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
i18n-codelens-mcp io.github.hepter/i18n-codelens-mcp
Inspect, audit and safely edit i18n locale JSON files from AI agents.
-
i18n-agent-action io.github.SamYuan1990/i18n-agent-action
An i18n github action for language translate
-
Make apps global-ready from your coding agent: analyze, translate, check and review i18n locally.
-
i18n toolkit for AI agents: MCP server, locale-file guardrails, undefined-keys gate.
-
intlpull io.github.intlpull/intlpull
AI-powered i18n platform with 50+ tools for translations, OTA releases, and more.
-
Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
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.
i18n-extractor
Extract strings and set up internationalization
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)
i18n-extractor
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 i18n-extractor publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of i18n-extractor publish no settings it asks for, so we do not compare settings.
What it can do: Sequa.AI · What it can do: i18n-extractor · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.