Dataiku MCP vs N8n
Dataiku MCP is an MCP server published by clssck. Marketplaces we read that list it: 1 (Official MCP Registry). N8n is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-04. 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 |  Dataiku MCP |  N8n |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Downloads/month (npm): 287 Downloads/week (npm): 163 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | Dataiku MCP | N8n |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (dataiku-mcp) | Remote server (gateway.pipeworx.io/n8n/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/clssck/dataiku_mcp | github.com/pipeworx-io/mcp-n8n |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
Dataiku MCP
MCP server for Dataiku DSS project, flow, and operations APIs.
N8n
n8n MCP — query your own n8n instance (BYO).
How to run each
Dataiku MCP As a local MCP server: npm package
claude mcp add --env "DATAIKU_API_KEY=<YOUR_DATAIKU_API_KEY>" --env "DATAIKU_URL=<YOUR_DATAIKU_URL>" --transport stdio dataiku-mcp -- npx -y dataiku-mcpRequires: DATAIKU_API_KEY (secret), DATAIKU_URL
N8n As a remote MCP server
claude mcp add --transport http n8n https://gateway.pipeworx.io/n8n/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only N8n has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Dataiku MCP asks for
DATAIKU_API_KEY (secret)DATAIKU_PROJECT_KEYDATAIKU_URL
Only N8n asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dataiku MCP · What it can do: N8n · Compare two other plugins
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.