Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs chat-recall

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). chat-recall is an MCP server published by munhq. Marketplaces we read that list it: 1 (Official MCP Registry). 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.AIchat-recall
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: 0.7.19
Downloads/month (npm): 5 334
Downloads/week (npm): 279
Forks (GitHub): 0
Stars (GitHub): 2
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 chat-recall
FactSequa.AIchat-recall
Marketplaces that list it11
Stars (GitHub) (differs)22 (better)2 (worse)
Pulls (Docker Hub) (differs)10 290No figure on Docker Hub
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequa)Remote server (chatrecall.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/munhq/chat-recall
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 301 (17 h 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.

chat-recall

In its own words, on Official MCP Registry:

One searchable history across every AI coding tool, with secret scanning and a shared task board.

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)

chat-recall As a remote MCP server

Claude Code
claude mcp add --transport http chat-recall https://chatrecall.dev/mcp

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

Only chat-recall has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of chat-recall 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 chat-recall asks for

  • CHAT_RECALL_DAEMON_IDLE_SECS
  • CHAT_RECALL_MCP_PROFILE
  • CHAT_RECALL_NO_DAEMON
  • CHAT_RECALL_SERVER

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

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