MCP as the Aspect Weaver
Cross-cutting concerns advised into tasks at execution time, governed by Camunda authorization
Cross-Cutting Process Concerns
(the “aspects” — provided by the engine, not by the diagram)
1. Process Variables
Live state of the running instance
2. Instance History
What has already happened in this instance
3. Audit Log API
Who-did-what across instances of this process
4. Semantic Lineage
How each variable came to its current value
5. Peer-Task / Peer-Instance State
What sibling tasks and processes are doing
6. Goal Registry
The outcome this task is ultimately serving
7. Preference Weights
Organizational guidance learned over time
8. Policy / Ontology Version
The rules and meanings in effect right now
Camunda 8.9 MCP Gateway
The Aspect Weaver
Mechanism • JSON-RPC 2.0 tool surface • Schema-guided invocation • Discoverable at runtime • Authorization per role / task • Every call is logged
Tools exposed (selected) • getProcessInstance(id) • searchProcessInstances(query) • readVariable(scope, name) • writeVariable(scope, name, value) • getInstanceHistory(id, since) • queryAuditLog(filter) • getLineage(variable) • getGoalContext(taskId) • getPreferenceWeights(decision)
Tasks Across the Cluster
(any AI-enabled task in any process can be advised)
Replenishment Task
Perishable Replenishment process
consults: history, lineage, preferences
Budget Reallocation Task
Campaign Orchestration process
consults: peer state, goal, history
Claims Triage Task
Insurance Adjudication process
consults: peer instances, lineage
Triage Re-Evaluation Task
MCI Field Triage process
consults: cluster vars, peer goals
Course-Correction Task
Bounty Campaign process
consults: history, preferences, goal
Aspect Oriented Process Management: the weaver mediates — the diagram doesn’t have to.
Adding an aspect = registering a new MCP tool. Removing one = revoking authorization. No BPMN re-deployment.
Camunda 8.9 MCP Gateway • Audit Log API • Conditional Events • Cluster Variables