Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs graperoot

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). graperoot is a plugin bundle for AI coding tools published by kunal12203. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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.AIgraperoot
Docker MCP Catalog Listed
Version: sha256:f4e0e271c5c5
Forks (GitHub): 5
Pulls (Docker Hub): 10 257
Stars (Docker Hub): 1
Stars (GitHub): 22
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.8.66
Forks (GitHub): 3
Stars (GitHub): 15
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 graperoot
FactSequa.AIgraperoot
Marketplaces that list it11
Stars (GitHub) (differs)22 (better)15 (worse)
Pulls (Docker Hub) (differs)10 257No figure on Docker Hub
Forks (GitHub) (differs)5 (better)3 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequa)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITProprietary
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/kunal12203/graperoot-plugin
Changes in the last 7 days00
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.

graperoot

In its own words, on Claude Code: claude-plugins-community:

Dual-graph code context engine for Claude Code. Builds a structural call graph and dependency graph of your codebase, then delivers precise file and symbol recommendations before Claude starts exploring. Reduces token usage by up to 60% and improves code accuracy by guiding Claude to the right files first. Supports TypeScript, JavaScript, Python, Go, Rust, Java, C/C++, and 10+ more languages. Install via pip, no source code required, fully compiled

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)

graperoot

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 graperoot 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 graperoot asks for

  • DUAL_GRAPH_PROJECT_ROOT

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

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

Where the data comes from: how the catalog is built