Camunda vs MeisterTask

MeisterTask ships small, clearly-labelled changes every few weeks — NEW or IMPROVED, one feature at a time. The spring run covered two distinct fronts: an MCP server that exposes projects, tasks and notes to AI assistants, and team workload plus capacity planning tools gated to Business and Enterprise plans. Everything since has been consolidation, including tables in Note, watcher automation, checklist item copying, and universal search reaching the mobile app.

The product is being extended at both ends of its user base. Upward, workload widgets and a cross-project capacity planner are the features that let it be sold to teams currently choosing heavier tools, and the plan gating makes that intent explicit. Outward, the MCP server treats AI assistants as a new client surface alongside web and mobile. The remaining work reads as parity-closing — mobile catching up to desktop search, Note gaining tables, automations reaching one more field — which is the shape of a product tidying its edges rather than opening a new one.

Automation coverage has expanded one trigger and one field at a time, so the next additions will most likely follow that pattern rather than arrive as a redesign. With the MCP server shipped, the open question the entries do not answer is whether it stays read-and-write across all plan tiers or becomes another Business-and-above feature.