Ext Ops Panel
Open dashboard
Comparison

Camunda BPM Process Engine vs SAP Business One

Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). SAP Business One is a plugin bundle for AI coding tools published by Aske Paustian. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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

Where each is published
MarketplaceCamunda BPM Process EngineSAP Business One
Docker MCP Catalog Listed
Version: sha256:fbea3848bcb6
Forks (GitHub): 5
Pulls (Docker Hub): 57 523
Stars (Docker Hub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Community marketplace askinator/sap-b1-plugin Not listed Listed
Version: 0.7.1
Forks (GitHub): 1
Stars (GitHub): 4
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 SAP Business One
FactCamunda BPM Process EngineSAP Business One
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)4 (worse)
Pulls (Docker Hub) (differs)57 523No figure on Docker Hub
Forks (GitHub) (differs)5 (better)1 (worse)
Last release (differs)Not published2026-10-16
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 bundle13
Licence (differs)MITSEE LICENSE IN LICENSE
Repository (differs)github.com/lepoco/mcp-camundagithub.com/askinator/sap-b1-plugin
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-15

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.

SAP Business One

In its own words, on Community GitHub marketplaces:

Workflow skills for a hosted SAP B1 Service Layer MCP server (added as a custom connector) for the sales/purchasing lifecycles, invoices, credit memos, payments, journal entries, service calls, master data, lookups, internal messages, and live dashboards and custom pages.

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

SAP Business One As a Claude Code plugin

Claude Code
/plugin marketplace add askinator/sap-b1-plugin
/plugin install sap-b1@sap-b1-plugins

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

Tools each declares

The marketplaces of SAP Business One publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Camunda BPM Process Engine · What it can do: SAP Business One · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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