Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs ARC-1

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). ARC-1 is an MCP server published by arc-mcp. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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

Where each is published
MarketplaceSequa.AIARC-1
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
Official MCP Registry Not listed Listed
Version: 1.5.2
Downloads/month (npm): 7 528
Downloads/week (npm): 2 195
Forks (GitHub): 65
Stars (GitHub): 220
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 ARC-1
FactSequa.AIARC-1
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)22 (worse)220 (better)
Pulls (Docker Hub) (differs)10 290No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)65 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequa)On your machine (arc-1)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 116, secrets among them: 1
Parts of the bundle (differs)Not a bundle23
LicenceMITMIT
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/arc-mcp/arc-1
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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.

ARC-1

In its own words, on Official MCP Registry:

MCP server for SAP ABAP systems

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)

ARC-1 As a local MCP server: npm package

Claude Code
claude mcp add --env "SAP_PASSWORD=<YOUR_SAP_PASSWORD>" --env "SAP_URL=<YOUR_SAP_URL>" --env "SAP_USER=<YOUR_SAP_USER>" --transport stdio arc-1 -- npx -y arc-1

Requires: SAP_PASSWORD (secret), SAP_URL, SAP_USER

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

Tools each declares

The marketplaces of ARC-1 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 ARC-1 asks for

  • ARC1_UI
  • ARC1_UI_ADDR
  • ARC1_UI_OPEN
  • SAP_ALLOWED_PACKAGES
  • SAP_ALLOW_DATA_PREVIEW
  • SAP_ALLOW_FREE_SQL
  • SAP_ALLOW_GIT_WRITES
  • SAP_ALLOW_TRANSPORT_WRITES
  • SAP_ALLOW_WRITES
  • SAP_BLOCKED_DATA_SOURCES
  • SAP_CLIENT
  • SAP_INSECURE
Show the remaining 5
  • SAP_LANGUAGE
  • SAP_PASSWORD (secret)
  • SAP_TRANSPORT
  • SAP_URL
  • SAP_USER

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

What it can do: Sequa.AI · What it can do: ARC-1 · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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