Camunda BPM Process Engine vs smile-webhooks
Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). smile-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fbea3848bcb6 Forks (GitHub): 5 Pulls (Docker Hub): 57 605 Stars (Docker Hub): 1 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated Forks (GitHub): 16 Stars (GitHub): 92 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 | smile-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (worse) | 92 (better) |
| Pulls (Docker Hub) (differs) | 57 605 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 (worse) | 16 (better) |
| 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 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/lepoco/mcp-camunda | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
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.
smile-webhooks
Receive and verify Smile API (getsmileapi.com) webhooks. Use when setting up a Smile webhook endpoint, verifying the Smile-Signature header (HMAC-SHA512 hex over the raw body), debugging Smile signature verification failures, or handling employment/income data events like ACCOUNT_CONNECTED, TASK_FINISHED, INCOMES_ADDED, EMPLOYMENTS_ADDED, IDENTITY_ADDED, and RECORD_COMPLETED. This is Smile API for Southeast Asian employment/income data — NOT Smile.io loyalty and NOT Smile Identity KYC.
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/camundasmile-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install smile-webhooks@webhook-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of smile-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of smile-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Camunda BPM Process Engine · What it can do: smile-webhooks · 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.