Ext Ops Panel
Open dashboard
Comparison

n8n vs Accordo — agent-native CRM framework

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). Accordo — agent-native CRM framework is a plugin bundle for AI coding tools published by Aetha. Marketplaces we read that list it: 1 (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
Marketplacen8nAccordo — agent-native CRM framework
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 660
Pulls (Docker Hub): 153 037
Stars (Docker Hub): 23
Stars (GitHub): 23 055
Not marked · First seen
Not listed
Community marketplace khaoss85/agent-crm Not listed Listed
Version: 0.1.0
No figure published
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

n8n vs Accordo — agent-native CRM framework
Factn8nAccordo — agent-native CRM framework
Marketplaces that list it11
Stars (GitHub) (differs)23 055No figure on GitHub
Pulls (Docker Hub) (differs)153 037No figure on Docker Hub
Forks (GitHub) (differs)3 660No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/n8n)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)42Not published
Environment variables it asks for (differs)3, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle12
LicenceMITMIT
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/khaoss85/agent-crm
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13

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

n8n

In its own words, on Docker MCP Catalog:

Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.

Accordo — agent-native CRM framework

In its own words, on Community GitHub marketplaces:

Build custom CRMs and Customer Hubs as code you own. For Smart CRM, the agent composes while deterministic policy governs; for CDP + CRM, Accordo is the process layer with bounded JSON imports and logical identity; no streaming ingestion, audience segmentation or CDP activation. Includes skills and a local project MCP; code generation stays dry-run until --apply.

How to run each

n8n As a local MCP server: Docker image

Claude Code
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --transport stdio n8n -- docker run -i --rm -e N8N_API_KEY mcp/n8n

Requires: N8N_API_KEY (secret)

Accordo — agent-native CRM framework As a Claude Code plugin

Claude Code
/plugin marketplace add khaoss85/agent-crm
/plugin install accordo@accordo

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

Tools each declares

The marketplaces of Accordo — agent-native CRM framework publish no list of tools, so we do not compare tools.

Settings each asks for

Only n8n asks for

  • MCP_MODE
  • N8N_API_KEY (secret)
  • N8N_API_URL

Only Accordo — agent-native CRM framework asks for

  • CRM_DB_PATH

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

What it can do: n8n · What it can do: Accordo — agent-native CRM framework · 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