Ext Ops Panel
Open dashboard
Comparison

Camunda BPM Process Engine vs rootly

Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). rootly is a plugin bundle for AI coding tools published by Rootly-AI-Labs. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 Enginerootly
Docker MCP Catalog Listed
Version: sha256:fbea3848bcb6
Forks (GitHub): 5
Pulls (Docker Hub): 57 503
Stars (Docker Hub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 2.2.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 2.2.0
Forks (GitHub): 0
Stars (GitHub): 1
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 rootly
FactCamunda BPM Process Enginerootly
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)14 (better)1 (worse)
Pulls (Docker Hub) (differs)57 503No figure on Docker Hub
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/camunda)Remote server (mcp.rootly.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle24
Licence (differs)MITApache-2.0
Repository (differs)github.com/lepoco/mcp-camundagithub.com/rootly-ai-labs/rootly-claude-plugin
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

rootly

In its own words, on Claude Code: claude-plugins-official:

Full-lifecycle incident management: deploy safety, incident response, on-call management, and retrospectives.

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

rootly As a Claude Code plugin

Claude Code
/plugin install rootly@claude-plugins-official

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

Tools each declares

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

Settings each asks for

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

What it can do: Camunda BPM Process Engine · What it can do: rootly · 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/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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