Ext Ops Panel
Open dashboard
Comparison

Camunda BPM Process Engine vs Engineering

Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). Engineering is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). As of our marketplace pass on 2026-10-12. 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
MarketplaceCamunda BPM Process EngineEngineering
Docker MCP Catalog Listed
Version: sha256:fbea3848bcb6
Forks (GitHub): 5
Pulls (Docker Hub): 57 480
Stars (Docker Hub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Not listed Listed
Version: 1.2.0
Forks (GitHub): 3 317
Stars (GitHub): 29 279
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

Camunda BPM Process Engine vs Engineering
FactCamunda BPM Process EngineEngineering
Marketplaces that list it11
Stars (GitHub) (differs)14 (worse)29 279 (better)
Pulls (Docker Hub) (differs)57 480No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)3 317 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/camunda)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle20
Licence (differs)MITNot stated
Repository (differs)github.com/lepoco/mcp-camundagithub.com/anthropics/knowledge-work-plugins
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

In its own words, on Docker MCP Catalog:

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.

Engineering

In its own words, on Claude: knowledge-work-plugins:

Streamline engineering workflows — standups, code review, architecture decisions, incident response, and technical documentation. Works with your existing tools or standalone.

How to run each

Camunda BPM Process Engine As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio camunda -- docker run -i --rm mcp/camunda

Engineering

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of Engineering publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Engineering publish no settings it asks for, so we do not compare settings.

What it can do: Camunda BPM Process Engine · What it can do: Engineering · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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