mcp/camunda repository overview

⁠Camunda BPM Process Engine MCP Server

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.

What is an MCP Server?⁠

⁠MCP Info

⁠Image Building Info

Attribute	Details
Dockerfile	https://github.com/lepoco/mcp-camunda/blob/4b50f37af26a66cced81895ba9b6d71b382ff022/Dockerfile⁠
Commit	4b50f37af26a66cced81895ba9b6d71b382ff022
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/camunda --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence	MIT License

⁠Available Tools (12)

⁠Tools Details

⁠Tool: complete_user_task

Complete a user task in the Camunda process engine. The task is identified by its unique task id.

⁠Tool: count_incidents

Count incidents for a specific BPMN process instance in the Camunda process engine. The process is identified by its process instance id or the business key.

⁠Tool: count_instances

Count active instances for a specific BPMN process definition in the Camunda process engine. The process is identified by its key. The response includes information about the number of active instances associated with the process definition.

⁠Tool: count_user_tasks

Count user tasks for a specific BPMN process instance in the Camunda process engine. The process is identified by its process instance id or the business key.

⁠Tool: count_variables

Count variables for a specific BPMN process in the Camunda process engine. The process is identified by its process instance id or the business key. The response information about the number of variables associated with the process instance.

⁠Tool: list_definitions

Retrieve all BPMN process definitions available in the Camunda BPM process engine. The response includes details such as tenant, version, deployment ID, and other metadata for each process definition. Allows narrowing down results by providing parts of the process key or name, and limiting the number of results returned.

⁠Tool: list_incidents

List incidents for a specific BPMN process instance in the Camunda process engine. The process is identified by its process instance id or the business key.

⁠Tool: list_instances

Retrieve the list of active instances for a specific BPMN process definition in the Camunda process engine. The process is identified by its key. The response includes details such as tenant, key, business key, process instance id, and other metadata for each process instance.

⁠Tool: list_user_tasks

List user tasks for a specific BPMN process instance in the Camunda process engine. The process is identified by its process instance id or the business key.

⁠Tool: list_variables

Retrieve the list of variables for a specific BPMN process in the Camunda process engine. The process is identified by its process instance id or the business key. The response includes details such as tenant, key, business key, process instance id, and other metadata for each process instance.

⁠Tool: resolve_incident

Requests the Cmaunda BPM process engine to resolve an incident. Resolving an incident allows the process instance to continue its execution.

⁠Tool: send_message

Send a message to a specific BPMN process instance in the Camunda process engine. The process is identified by its process instance id or the business key.

⁠Use this MCP Server

{
  "mcpServers": {
    "camunda": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CAMUNDA_HOST",
        "mcp/camunda"
      ],
      "env": {
        "CAMUNDA_HOST": "http://host.docker.internal:8080/"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠