Skip to main content
Glama
Camunda Engine MCP Server

Camunda Engine MCP Server

by maksdizzy

๐Ÿญ Camunda Engine MCP Server

Production Ready Docker MCP Camunda

A Model Context Protocol (MCP) server that enables AI assistants to interact with Camunda Platform workflow engine. Provides 21 specialized tools for complete workflow automation and process management.

โœ… PRODUCTION READY - Fully tested, containerized, and ready for deployment.

๐Ÿš€ Quick Start

1. Start the Server

git clone <repo-url>
cd camunda-engine-mcp
docker-compose up -d

2. Configure Claude Desktop

Add to your Claude Desktop MCP settings:

{
  "mcpServers": {
    "camunda": {
      "command": "docker",
      "args": [
        "exec", "-i",
        "-e", "CAMUNDA_BASE_URL=https://your-camunda-instance.com/engine-rest",
        "-e", "CAMUNDA_USERNAME=your-username",
        "-e", "CAMUNDA_PASSWORD=your-password",
        "camunda-mcp-server",
        "node", "build/index.js"
      ]
    }
  }
}

3. Restart Claude Desktop

Completely close and restart Claude Desktop to load the MCP server.

4. Test Connection

Try these commands in Claude Desktop:

Show me all available processes in Camunda
Get the list of current tasks from Camunda
Deploy BPMN from file /workspace/bpmn/simple-process.bpmn

Related MCP server: n8n-manager-mcp

๐ŸŽฏ Features

  • 21 MCP Tools for complete Camunda workflow management

  • Process Management - Deploy, start, monitor BPMN processes

  • Task Management - Handle user tasks and forms

  • Large File Support - Deploy big BPMN files via file paths

  • Production Ready - Docker, monitoring, health checks

  • Real-time Integration - Direct connection to live Camunda instances

๐Ÿ“ File Deployment

For large BPMN/form files, place them in directories:

./bpmn-files/your-process.bpmn    # โ†’ /workspace/bpmn/your-process.bpmn
./forms/your-form.form            # โ†’ /workspace/forms/your-form.form

Then use file paths instead of content:

Deploy BPMN from file /workspace/bpmn/your-process.bpmn

๐Ÿ“š Documentation

๐Ÿ”ง Environment Variables

CAMUNDA_BASE_URL=https://your-camunda-instance.com/engine-rest
CAMUNDA_USERNAME=your-username
CAMUNDA_PASSWORD=your-password

๐Ÿงช Health Check

docker exec camunda-mcp-server npm run health-check

๐Ÿ“ž Support


Ready to automate your workflows with AI? Start with the Quick Start above! ๐Ÿš€

Available Tools

21 tools
activateProcessInstanceB

Activate a suspended process instance

Inputs: processInstanceId (required).

completeTaskC

Complete a task

Inputs: taskId (required), variables.

deleteDeploymentB

Delete a deployment by id

Inputs: deploymentId (required), cascade, skipCustomListeners, skipIoMappings.

deleteProcessInstanceC

Delete a process instance

Inputs: processInstanceId (required), reason, skipCustomListeners, skipIoMappings, +1 more.

deployBpmnB

Deploy a BPMN process definition from content or file

Inputs: deploymentName (required), bpmnContent (required), fileName, enableDuplicateFiltering, +1 more.

deployFormB

Deploy a Camunda Form from content or file

Inputs: deploymentName (required), formContent (required), fileName.

getActivityInstancesB

Get activity instances for a process instance

Inputs: processInstanceId (required).

getDeploymentResourcesC

Get resources of a deployment

Inputs: deploymentId (required).

getDeploymentsC

Get a list of deployments

Inputs: id, name, nameLike, source, +2 more.

getIncidentsB

Get incidents (errors) in processes

Inputs: processInstanceId, incidentType, maxResults.

getProcessDefinitionsC

Get a list of process definitions

Inputs: latestVersionOnly, firstResult, maxResults.

getProcessInstancesC

Get a list of process instances

Inputs: processDefinitionId, processDefinitionKey, businessKey, firstResult, +1 more.

getProcessVariablesC

Get variables of a process instance

Inputs: processInstanceId (required).

getStartFormB

Get the start form for a process definition

Inputs: processDefinitionId, processDefinitionKey.

getTaskFormC

Get the form for a task

Inputs: taskId (required).

getTasksC

Get a list of tasks

Inputs: processInstanceId, taskDefinitionKey, assignee, firstResult, +1 more.

setProcessVariablesA

Set/update variables of a process instance

Inputs: processInstanceId (required), variables (required).

startProcessInstanceC

Start a new process instance

Inputs: processDefinitionId (required), processDefinitionKey, variables, businessKey.

submitStartFormC

Submit a start form and start process instance

Inputs: processDefinitionId, processDefinitionKey, variables, businessKey.

submitTaskFormC

Submit a task form

Inputs: taskId (required), variables (required).

suspendProcessInstanceB

Suspend a process instance

Inputs: processInstanceId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct operation (e.g., deployment, process instance, task, variable, form) with clear boundaries. Overlapping purposes like startProcessInstance and submitStartForm are differentiated by direct vs. form-based start.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in camelCase (e.g., deployBpmn, getTasks, completeTask). No mixing of styles or irregular abbreviations.

    Tool Count5/5

    21 tools appropriately cover a BPM engine's core operations without being excessive. The count is well-scoped for the domain's complexity.

    Completeness5/5

    The tool surface provides CRUD operations for deployments, process instances, tasks, and variables, plus form handling and incident querying. No obvious gaps for typical lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers