I have worked on creating a MCP server for Operaton. You can find it at https://www.npmjs.com/package/operaton-mcp
The MCP server is in an early development phase. However, it covers already large portions of the Operaton REST API. It provides already
- Process Definition inspection and process instances
- Task claim, edit, complete
- User administration
- Process instance migration
- Incident management
- Job management
- Deployment
❯ Show me tasks claimed by me
⏺ Tasks Claimed by "demo" User (2 tasks):
1. Assign Reviewer (Task ID: 264338f2)
- Process: ReviewInvoice
- Priority: 50
- Created: 2026-03-17
- Status: Created
- Form: embedded:app:forms/assign-reviewer.html
2. Assign Reviewer (Task ID: 266abdf2)
- Process: ReviewInvoice
- Priority: 50
- Created: 2026-03-17
- Status: Created
- Form: embedded:app:forms/assign-reviewer.html
Other Available Tasks (5 unassigned):
- 3x "Approve Invoice" tasks
- 2x "Prepare Bank Transfer" tasks (due 2026-03-24)
❯ Which process instances can be migrated?
⏺ Migratable Process Instances:
There are 5 eligible instances that can be migrated:
┌──────────────────────────────────────┬─────────┬─────────────┐
│ Instance ID │ Version │ Status │
├──────────────────────────────────────┼─────────┼─────────────┤
│ 25341320-2225-11f1-ba79-feb948cfc98c │ V1 │ ✅ Eligible │
├──────────────────────────────────────┼─────────┼─────────────┤
│ 261cc5a0-2225-11f1-ba79-feb948cfc98c │ V1 │ ✅ Eligible │
├──────────────────────────────────────┼─────────┼─────────────┤
│ 2649c8b1-2225-11f1-ba79-feb948cfc98c │ V2 │ ✅ Eligible │
├──────────────────────────────────────┼─────────┼─────────────┤
│ 2650cdc1-2225-11f1-ba79-feb948cfc98c │ V2 │ ✅ Eligible │
├──────────────────────────────────────┼─────────┼─────────────┤
│ a64bf595-222b-11f1-ba79-feb948cfc98c │ V2 │ ✅ Eligible │
└──────────────────────────────────────┴─────────┴─────────────┘
Blocked Instances (cannot migrate):
There are 2 instances with active call activities that block migration:
- 26341e7a-2225-11f1-ba79-feb948cfc98c (V1)
- 265fc22a-2225-11f1-ba79-feb948cfc98c (V2)
These instances have active child processes that fall outside migration scope. You'd need to wait for their call activities
to complete before migrating them.
❯ migrate eligible instances
⏺ Migration successful! ✅
Both eligible V1 instances have been migrated to V2:
┌──────────────────────────────────────┬─────────────┬────────────────┐
│ Instance ID │ Status │ New Definition │
├──────────────────────────────────────┼─────────────┼────────────────┤
│ 25341320-2225-11f1-ba79-feb948cfc98c │ ✅ Migrated │ invoice:2 │
├──────────────────────────────────────┼─────────────┼────────────────┤
│ 261cc5a0-2225-11f1-ba79-feb948cfc98c │ ✅ Migrated │ invoice:2 │
└──────────────────────────────────────┴─────────────┴────────────────┘
Summary:
- 2 instances migrated from Invoice V1 → V2
- 2 instances blocked (active call activities) - remain unmigrated
- Batch completed in 129ms
⏺ I'll migrate the eligible instances from V1 to V2. Let me start by generating a migration plan:
I kindly ask for testing it. Please report issues & ideas to




