Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs oma

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). oma is a plugin bundle for AI coding tools published by First Fluke. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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

Where each is published
MarketplaceSequa.AIoma
Docker MCP Catalog Listed
Version: sha256:f4e0e271c5c5
Forks (GitHub): 5
Pulls (Docker Hub): 10 636
Stars (Docker Hub): 1
Stars (GitHub): 22
Not marked · First seen
Not listed
Community marketplace first-fluke/oh-my-agent Not listed Listed
Version: 20.13.0
Forks (GitHub): 150
Stars (GitHub): 1 354
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

Sequa.AI vs oma
FactSequa.AIoma
Marketplaces that list it11
Stars (GitHub) (differs)22 (worse)1 354 (better)
Pulls (Docker Hub) (differs)10 636No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)150 (better)
Last release (differs)Not published2026-10-24
Where it runs (differs)On your machine (mcp/sequa)Remote server (mcp.context7.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Hooks it runs (differs)Not published6
Parts of the bundle (differs)Not a bundle52
LicenceMITMIT
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/first-fluke/oh-my-agent
Changes in the last 7 days (differs)07
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

In its own words, on Docker MCP Catalog:

Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.

oma

In its own words, on Community GitHub marketplaces:

Portable multi-agent harness for .agents-based skills and workflows

How to run each

Sequa.AI As a local MCP server: Docker image

Claude Code
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequa

Requires: API_KEY (secret)

oma As a Claude Code plugin

Claude Code
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only oma has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of oma publish no list of tools, so we do not compare tools.

Settings each asks for

Only Sequa.AI asks for

  • API_KEY (secret)
  • MCP_SERVER_URL

Only oma asks for

  • SERENA_LOG_LEVEL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Sequa.AI · What it can do: oma · 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.

Where the data comes from: how the catalog is built