BPMN Kit vs N8n
BPMN Kit is an MCP server published by bpmnkit. 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-10-24. 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 |  BPMN Kit |  N8n |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.0 Downloads/month (npm): 1 509 Downloads/week (npm): 297 Forks (GitHub): 2 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 0.1.3 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 | BPMN Kit | N8n |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (@bpmnkit/cli) | 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 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bpmnkit/bpmnkit | github.com/pipeworx-io/mcp-n8n |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
BPMN Kit
Create, validate, simulate and deploy Camunda 8 BPMN processes, forms and DMN from an agent.
N8n
n8n MCP — query your own n8n instance (BYO).
How to run each
BPMN Kit As a local MCP server: npm package
claude mcp add --env "ZEEBE_CLIENT_SECRET=<YOUR_ZEEBE_CLIENT_SECRET>" --transport stdio bpmnkit -- npx -y @bpmnkit/cli proxy mcpRequires: ZEEBE_CLIENT_SECRET (secret)
N8n As a remote MCP server
claude mcp add --transport http n8n https://gateway.pipeworx.io/n8n/mcpCommands 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
The marketplaces of N8n publish no settings it asks for, so we do not compare settings.
What it can do: BPMN Kit · 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.