--- collection: workflow-orchestration collection_name: Background Jobs & Orchestration week_start: 2026-07-27 title: MCP servers graduate from experimental to operational release_count: 14 generated: 2026-08-03 canonical: https://releases.sh/collections/workflow-orchestration/digest/2026-07-27 --- # MCP servers graduate from experimental to operational Inngest exposes MCP tools from its v2 REST API and n8n saves execution data only after MCP tool calls complete, while both platforms harden their run-control APIs with cancel and rerun endpoints. ### MCP servers become production-grade tools The week's strongest signal came from how each platform handled its Model Context Protocol support. [Inngest's v1.40.0 server](/release/rel_EvNpZdH6NlHnkdOSbun7e-v1-40-0) rebuilt its MCP tool list to align with the v2 REST API and CLI, exposing a richer set of tools that developers can invoke directly from AI assistants. The change moves MCP from a side experiment to a first-class interface — the same operations you'd script via `inngest` CLI are now discoverable by LLMs. On the n8n side, [n8n@2.33.3](/release/rel_i9-xipyQwIdNZTa9l2K2l-n8n-2-33-3) fixed a critical correctness issue in the MCP Server Trigger node: execution data is now persisted only after the tool call completes, preventing premature saves that could leave incomplete state in the database. Both releases speak to the same maturation — MCP isn't new anymore, but making it reliable enough for production workflows is the work of this quarter. ### Run-control APIs expand on both sides Inngest and Temporal each shipped notable improvements to how you manage running work. [Inngest v1.39.0](/release/rel_SieISt5g9r3TkjyKAUJVm-v1-39-0) added a v2 cancel-run endpoint (`POST /api/v2/runs/{run_id}/cancel`) and a rerun-from-step endpoint that lets you resume a failed run at a specific step with custom input — a long-requested capability for debugging and partial retries. Temporal's [Go SDK v1.47.0](/release/rel_cw5uvc_RrilNTLhyIPc7--v1-47-0) promoted several user metadata fields (StaticSummary, StaticDetails, CurrentDetails) out of experimental status, and introduced automatic enrollment in poller autoscaling when the namespace advertises support. The `PreferredVersionProvider` option on `worker.Options` is also new, letting SDKs influence which version gets recorded during polling — small but meaningful for teams running multi-version deployments. ### n8n's 2.33.0 feature release and patch cadence n8n's [2.33.0](/release/rel_Q8cFu6mW3dvWOHiW5W-uG-n8n-2-33-0) brought the AI Builder forward: workflow verification now halts at send-and-wait gates inside loops, and assistant replies stay in the user's language during tool-heavy turns. The release also added a `Date` node for timezone-aware date manipulation, unblocking workflows that need to handle scheduling across time zones. A follow-up [2.33.1](/release/rel_dc5ZwENPpr-MHIjt8bZfL-n8n-2-33-1) exposed workflow hook context to lifecycle external hooks, giving self-hosted operators more visibility into workflow state transitions. On the patch side, [2.33.2](/release/rel_IuvJwQ4udUJeFcwOzGMc3-n8n-2-33-2) fixed an AI Assistant sandbox provider selection bug, and the backport [2.32.6](/release/rel_AFIiFIQU4lK-ue4Q-hEA3-n8n-2-32-6) accepted 5-field cron expressions in the schedule trigger — a compatibility fix for users migrating from other cron systems. ### Trigger.dev tightens deployment and session control [Trigger.dev v4.5.9](/release/rel_1PjKH_lDx3ZQQZ2IYlEH2-trigger-dev-v4-5-9) included breaking changes — the release notes flagged them explicitly — though the full scope is detailed in their changelog. The preceding [v4.5.8](/release/rel_fke4E_rw5iMh5KkAgIwLA-trigger-dev-v4-5-8) improved task run preservation during re-deploys, meaning active runs are less likely to be orphaned when you push new code. The trend across both versions is toward safer hot-reload: keeping sessions alive through deployment cycles rather than forcing a hard cutover. ### Security and observability patches Several smaller fixes rounded out the week. Inngest's [JS SDK v4.14.0](/release/rel_IVhotSn542R1y8oFz0FGD-inngest-4-14-0) began extracting AI call latency into execution metadata, and its [OpenTelemetry package](/release/rel_p2xC3HwSRTIgCRVWmIr1Q-inngest-otel-0-2-2) added a marker to identify the OTel provider. n8n backported a security audit fix to [2.32.7](/release/rel_1InTsiNF5JaiS4TXnC2j4-n8n-2-32-7) and [2.31.7](/release/rel_KwRZDDGQPmEYdPGFpbtiM-n8n-2-31-7), both addressing how audit risk reporters are imported — a small but important hardening of the security scanning pipeline. ## Releases covered ### Inngest - [v1.40.0](https://releases.sh/release/rel_EvNpZdH6NlHnkdOSbun7e-v1-40-0) - [v1.39.0](https://releases.sh/release/rel_SieISt5g9r3TkjyKAUJVm-v1-39-0) - [inngest@4.14.0](https://releases.sh/release/rel_IVhotSn542R1y8oFz0FGD-inngest-4-14-0) - [@inngest/otel@0.2.2](https://releases.sh/release/rel_p2xC3HwSRTIgCRVWmIr1Q-inngest-otel-0-2-2) ### n8n - [n8n@2.33.3](https://releases.sh/release/rel_i9-xipyQwIdNZTa9l2K2l-n8n-2-33-3) - [n8n@2.33.0](https://releases.sh/release/rel_Q8cFu6mW3dvWOHiW5W-uG-n8n-2-33-0) - [n8n@2.33.1](https://releases.sh/release/rel_dc5ZwENPpr-MHIjt8bZfL-n8n-2-33-1) - [n8n@2.33.2](https://releases.sh/release/rel_IuvJwQ4udUJeFcwOzGMc3-n8n-2-33-2) - [n8n@2.32.6](https://releases.sh/release/rel_AFIiFIQU4lK-ue4Q-hEA3-n8n-2-32-6) - [n8n@2.32.7](https://releases.sh/release/rel_1InTsiNF5JaiS4TXnC2j4-n8n-2-32-7) - [n8n@2.31.7](https://releases.sh/release/rel_KwRZDDGQPmEYdPGFpbtiM-n8n-2-31-7) ### Temporal - [v1.47.0](https://releases.sh/release/rel_cw5uvc_RrilNTLhyIPc7--v1-47-0) ### Trigger.dev - [trigger.dev v4.5.9](https://releases.sh/release/rel_1PjKH_lDx3ZQQZ2IYlEH2-trigger-dev-v4-5-9) - [trigger.dev v4.5.8](https://releases.sh/release/rel_fke4E_rw5iMh5KkAgIwLA-trigger-dev-v4-5-8)