What it can do: Camunda BPM Process Engine
MCP server · lepoco
What Camunda BPM Process Engine declares, asks for and runs, according to the marketplaces we read. Runs on your machine, in a container started from this image: mcp/camunda. Tools it declares: 12. Environment variables it asks for: 1, secrets among them: 0. As of our marketplace pass on 2026-10-12.
This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.
Where it runs
- Runs on your machine, in a container started from this image:
mcp/camunda
What it declares
Tools it declares: 12. As declared on: Docker MCP Catalog.
complete_user_taskcount_incidentscount_instancescount_user_taskscount_variableslist_definitionslist_incidentslist_instanceslist_user_taskslist_variablesresolve_incidentsend_message
Prompts and resources: the marketplaces we read do not publish them.
What it asks for
Environment variables it asks for: 1, secrets among them: 0. As declared on: Docker MCP Catalog.
CAMUNDA_HOST
Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.
What it runs besides MCP
None of the marketplaces we read lists hooks, commands, agents or language servers for it.
Who answers for it
lepoco
- No marketplace we read marks it or its publisher as verified.
- License: MIT.
- Last change we saw: 2026-10-12.
How it has changed
Its tools, settings, hooks and composition have not changed since we started watching it.
In context
- Median number of secrets an MCP server asks for on the marketplaces we read: 0.0. This one asks for: 0.
- Share of MCP servers that run on a remote server: 63%.
Where it is published and how its figures have moved
Compare it side by side with similar plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.