CIB Seven MCP Server

Look up a CIB Seven process instance by its ID. Returns the instance's current state, definition reference, business key, and suspension status.

Use this when you have a specific process instance ID and need to understand its current state. If you only have a business key or definition key, use list_process_instances instead.

Key response fields:

• suspended: true means manually paused by an operator

• ended: true means the process completed or was cancelled

• businessKey: the domain identifier (e.g. order number, case ID)

• definitionId: use this to fetch the BPMN XML via get_process_definition_xml

Search for process instances using filters. Uses the history API to find both running and completed instances.

Use this when you need to find process instances by business key, definition key, or state. Returns an array of historic process instances.

Filter options:

• processDefinitionKey: the BPMN process ID (e.g., "orderProcess")

• businessKey: domain identifier (e.g., "ORDER-12345")

• state: ACTIVE, COMPLETED, SUSPENDED, or EXTERNALLY_TERMINATED

• maxResults: limit results (default 25)

• firstResult: offset for pagination

List open incidents in the process engine. Incidents record things that went wrong during execution.

Key incident types:

• failedJob: a service task or timer threw an exception and the engine gave up retrying (retries=0)

• failedExternalTask: an external task worker reported a failure

Use without filters to see all open incidents. Filter by processInstanceId to see incidents for a specific process.

Get the execution trace for a process instance — every activity that ran, in order.

This shows you exactly what happened: which tasks executed, in what order, and how long each took. Activities with a startTime but no endTime are currently executing or waiting.

Key fields:

• activityType: startEvent, serviceTask, userTask, exclusiveGateway, etc.

• activityName: human-readable name from the BPMN model

• startTime/endTime: when the activity started and finished

• durationInMillis: how long it took (null if still running)

• canceled: true if the activity was interrupted

Get all variables for a process instance. Variables hold the data that drives process execution — form inputs, API responses, decision results.

Sensitive variable values may be redacted (shown as [REDACTED]) based on configured patterns.

Common variable patterns:

• Error flags or status fields that indicate why a process is waiting

• Retry counters that show how many times something was attempted

• Input data from forms or API calls

Fetch the BPMN XML model for a process definition. This is the blueprint — it shows the expected flow of the process.

Use the definitionId from get_process_instance to fetch the model. The XML includes all activities, gateways, sequence flows, and conditions. Diagram layout elements are stripped for readability.

Read the XML to understand:

• The expected happy path (sequence of activities)

• Gateway conditions (what determines which path is taken)

• Error boundary events (what happens when activities fail)

• Timer events (scheduled waits or timeouts)

Get job execution details for a process instance. Jobs are units of work the engine executes — service tasks, timers, message events.

Key fields:

• retries: how many retry attempts remain. 0 means the engine gave up and created an incident.

• exceptionMessage: the error from the last failed execution attempt

• dueDate: when the job is scheduled to execute (for timers)

• suspended: true if the job is paused