Camunda BPM Process Engine vs Vertical Flows
Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vertical Flows is an MCP server published by verticalflows.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  Camunda BPM Process Engine |  Vertical Flows |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fbea3848bcb6 Forks (GitHub): 5 Pulls (Docker Hub): 57 519 Stars (Docker Hub): 1 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.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
| Fact | Camunda BPM Process Engine | Vertical Flows |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 57 519 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/camunda) | Remote server (verticalflows.com/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/lepoco/mcp-camunda | github.com/vertical-flows/verticalflows |
| 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 | Responded 12 h ago, requires a key |
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
Camunda BPM Process Engine
Tools to interact with the Camunda 7 Community Edition Engine using the Model Context Protocol (MCP). Whether you're automating workflows, querying process instances, or integrating with external systems, Camunda MCP Server is your agentic solution for seamless interaction with Camunda.
Vertical Flows
View client requests, prepare actions and approve work within your firm's permissions.
How to run each
Camunda BPM Process Engine As a local MCP server: Docker image
claude mcp add --transport stdio camunda -- docker run -i --rm mcp/camundaVertical Flows As a remote MCP server
claude mcp add --transport http agent-gateway https://verticalflows.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vertical Flows has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Vertical Flows publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Vertical Flows publish no settings it asks for, so we do not compare settings.
What it can do: Camunda BPM Process Engine · What it can do: Vertical Flows · 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.