Camunda BPM Process Engine vs Claude SOPs
Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). Claude SOPs is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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 |  Claude SOPs |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fbea3848bcb6 Forks (GitHub): 5 Pulls (Docker Hub): 57 542 Stars (Docker Hub): 1 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Community marketplace danielrosehill/claude-code-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 Stars (GitHub): 3 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 | Claude SOPs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 57 542 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/camunda) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/lepoco/mcp-camunda | github.com/danielrosehill/claude-sops |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-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
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.
Claude SOPs
Keep your own standard operating procedures — the recurring things you do a particular way — as a private, versioned library of markdown files the agent reads on demand and follows. Distinct from sop-writer, which authors printed SOP documents for other people; these are procedures an agent executes. One delimited block in your CLAUDE.md points at the library, a generated INDEX.md carries id, title and a 'use when' trigger for each procedure, and exactly one file is read once a situation matches — so a library of forty procedures costs one table to consult rather than forty resident skill descriptions. Seven skills cover setup, run, write, edit, list, retire and sync. Procedures live in ~/.claude-user-data/sops/ as flat readable files inside a private git repo, mirrored across machines; the plugin repo never holds one. Each SOP declares an autonomy level (auto, confirm, confirm-each, manual) that records a default rather than granting permission, and a last_verified date meaning the procedure was seen to work
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/camundaClaude SOPs As a Claude Code plugin
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install sop-library@danielrosehillCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Claude SOPs publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Claude SOPs publish no settings it asks for, so we do not compare settings.
What it can do: Camunda BPM Process Engine · What it can do: Claude SOPs · 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.