Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs Code-Graph-RAG

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Code-Graph-RAG is an MCP server published by vitali87. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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.AICode-Graph-RAG
Docker MCP Catalog Listed
Version: sha256:f4e0e271c5c5
Forks (GitHub): 5
Pulls (Docker Hub): 10 959
Stars (Docker Hub): 1
Stars (GitHub): 22
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.0
Forks (GitHub): 713
Stars (GitHub): 5 342
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 Code-Graph-RAG
FactSequa.AICode-Graph-RAG
Marketplaces that list it11
Stars (GitHub) (differs)22 (worse)5 342 (better)
Pulls (Docker Hub) (differs)10 959No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)713 (better)
Last release (differs)Not published2026-11-08
Where it runs (differs)On your machine (mcp/sequa)On your machine (code-graph-rag)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 19, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/vitali87/code-graph-rag
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-11-02

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.

Code-Graph-RAG

In its own words, on Official MCP Registry:

Knowledge-graph RAG for multi-language codebases: index, query and edit code in natural language.

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)

Code-Graph-RAG As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CYPHER_API_KEY=<YOUR_CYPHER_API_KEY>" --env "ORCHESTRATOR_API_KEY=<YOUR_ORCHESTRATOR_API_KEY>" --transport stdio code-graph-rag -- uvx code-graph-rag mcp-server

Requires: CYPHER_API_KEY (secret), ORCHESTRATOR_API_KEY (secret)

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

Tools each declares

The marketplaces of Code-Graph-RAG 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 Code-Graph-RAG asks for

  • CYPHER_API_KEY (secret)
  • CYPHER_MODEL
  • CYPHER_PROVIDER
  • MEMGRAPH_HOST
  • MEMGRAPH_PORT
  • ORCHESTRATOR_API_KEY (secret)
  • ORCHESTRATOR_MODEL
  • ORCHESTRATOR_PROVIDER
  • TARGET_REPO_PATH

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

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