Camunda BPM Process Engine vs io.github.chrischall/workday-mcp
Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.chrischall/workday-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  io.github.chrischall/workday-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fbea3848bcb6 Forks (GitHub): 5 Pulls (Docker Hub): 57 526 Stars (Docker Hub): 1 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.9 Downloads/month (npm): 2 688 Downloads/week (npm): 800 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
| Fact | Camunda BPM Process Engine | io.github.chrischall/workday-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 57 526 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/camunda) | On your machine (workday-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 4, secrets among them: 0 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/lepoco/mcp-camunda | github.com/chrischall/workday-mcp |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-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
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.
io.github.chrischall/workday-mcp
Read-only Workday for Claude — fetch tasks, pay, benefits via your signed-in session
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/camundaio.github.chrischall/workday-mcp As a local MCP server: npm package
claude mcp add --env "WORKDAY_TENANT=<YOUR_WORKDAY_TENANT>" --transport stdio workday-mcp -- npx -y workday-mcpRequires: WORKDAY_TENANT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.chrischall/workday-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Only Camunda BPM Process Engine asks for
CAMUNDA_HOST
Only io.github.chrischall/workday-mcp asks for
WORKDAY_DEBUGWORKDAY_HOSTWORKDAY_TENANTWORKDAY_WS_PORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Camunda BPM Process Engine · What it can do: io.github.chrischall/workday-mcp · 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. 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.