Camunda Engine MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAMUNDA_BASE_URL | Yes | The base URL of the Camunda Engine REST API. | |
| CAMUNDA_PASSWORD | Yes | The password for Camunda authentication. | |
| CAMUNDA_USERNAME | Yes | The username for Camunda authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getProcessDefinitionsC | Get a list of process definitions |
| getProcessInstancesC | Get a list of process instances |
| startProcessInstanceC | Start a new process instance |
| getTasksC | Get a list of tasks |
| completeTaskC | Complete a task |
| deployBpmnB | Deploy a BPMN process definition from content or file |
| getDeploymentsC | Get a list of deployments |
| deleteDeploymentB | Delete a deployment by id |
| getDeploymentResourcesC | Get resources of a deployment |
| deployFormB | Deploy a Camunda Form from content or file |
| getTaskFormC | Get the form for a task |
| submitTaskFormC | Submit a task form |
| getStartFormB | Get the start form for a process definition |
| submitStartFormC | Submit a start form and start process instance |
| getProcessVariablesC | Get variables of a process instance |
| setProcessVariablesA | Set/update variables of a process instance |
| getActivityInstancesB | Get activity instances for a process instance |
| getIncidentsB | Get incidents (errors) in processes |
| deleteProcessInstanceC | Delete a process instance |
| suspendProcessInstanceB | Suspend a process instance |
| activateProcessInstanceB | Activate a suspended process instance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
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.
All tools follow a consistent verb_noun pattern in camelCase (e.g., deployBpmn, getTasks, completeTask). No mixing of styles or irregular abbreviations.
21 tools appropriately cover a BPM engine's core operations without being excessive. The count is well-scoped for the domain's complexity.
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.