n8n vs Re:port Flow MCP
n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). Re:port Flow MCP is an MCP server published by re-port-flow. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
| Marketplace |   n8n |   Re:port Flow MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:061cdb8fbaa7 Forks (GitHub): 3 672 Pulls (Docker Hub): 155 862 Stars (Docker Hub): 23 Stars (GitHub): 23 115 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 297 Downloads/week (npm): 99 Forks (GitHub): 1 Stars (GitHub): 1 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
| Fact | n8n | Re:port Flow MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 23 115 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 155 862 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 672 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/n8n) | Remote server (mcp.re-port-flow.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 4, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/czlonkowski/n8n-mcp | github.com/re-port-flow/reportflow-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (2 days 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
n8n
Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.
Re:port Flow MCP
Generate PDF reports from Re:port Flow templates via Claude and other AI agents.
How to run each
n8n As a local MCP server: Docker image
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --transport stdio n8n -- docker run -i --rm -e N8N_API_KEY mcp/n8nRequires: N8N_API_KEY (secret)
Re:port Flow MCP As a remote MCP server
claude mcp add --transport http reportflow-mcp https://mcp.re-port-flow.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Re:port Flow MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Re:port Flow MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only n8n asks for
MCP_MODEN8N_API_KEY (secret)N8N_API_URL
Only Re:port Flow MCP asks for
REPORTFLOW_API_BASE_URLREPORTFLOW_AUTH_URLREPORTFLOW_CLIENT_IDREPORTFLOW_TOKEN_STORE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: n8n · What it can do: Re:port Flow MCP · 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.