Camunda 8.9 MCP Gateway — Inter-Process MCI Collaboration
Model Context Protocol enabling ambient coordination between independent process instances
Field Triage Agent
Publishes via MCP: • writeVariable: METHANE report • writeVariable: SALT distribution Ambient Reaction: • Conditional: ambulances ≥ 8 → Re-triage Expectant patients
Transport Agent
Queries via MCP: • searchInstances: hospital capacity + diversion status Ambient Reaction: • Conditional: diversion = true → Reroute to capable facility
The MCP Value Proposition
Before: 11 point-to-point flows, 4 pools After: 4 agents × 1 gateway, 0 wiring Result: New agents discover instantly
writeVariable
searchProcessInstances
CAMUNDA 8.9 MCP GATEWAY + CLUSTER VARIABLES
searchProcessInstances · writeVariable · createProcessInstance · Incident Tools · Authorization
Single governed interface — every agent reads from and writes to the same cluster state
search | write
search | create | write
Hospital Surge Agent
Queries via MCP: • searchInstances: IMMEDIATE patients, this incident Publishes via MCP: • writeVariable: OR capacity • writeVariable: diversion flag Ambient Reaction: • methane ≠ null → activate surge
EOC Coordination Agent
Queries via MCP: • searchInstances: all transport + hospital instances Invokes via MCP: • createProcessInstance: mutual-aid-request Publishes via MCP: • writeVariable: ambulances = 10
Ambient Coordination Cycle
1. EOC writeVariable: ambulances_available = 10 2. Conditional Event fires in Field Triage 3. SALT re-triage: Expectant → Immediate 4. Triage writeVariable: updated SALT results 5. Hospital queries MCP → sees new Immediate count No messages sent. Shared state coordinates.
MCP = Access | Ontology = Understanding
searchProcessInstances returns structured data SALT / MUCC / ICS semantics tell the agent what it means MCP = data pipeline; ontology = decision logic Camunda 8.9: first platform where both share one governed interface
Figure 4.4 — Camunda 8.9 MCP Gateway: Hub-and-Spoke MCI Collaboration | S7-MCI | April 2026