2026 年 9 月

September 2026 release notes for Maestro in Automation Cloud and Test Cloud.

September 3, 2026

MCP ツールをフローで直接設定および管理する

Maestro Flowで、自律型エージェント ノードによって、モデル コンテキスト プロトコル (MCP) ツールに対するより豊富な制御がサポートされるようになりました。引数ごとの記述を編集したり、ツールの完全な入力/出力スキーマを表示したり、各引数の値の取得方法 (実行時にエージェントが決定するか、エージェント変数にバインドするか、機密とマークできる固定値) を選択できます。MCP サーバーで、ツールを自動的に検出するだけでなく、明示的な [ツールを更新 ] アクションも公開され、Agent Hub からツール リストをライブで取得できるようになりました。

詳細については、「 エージェント」をご覧ください。

Keep MCP tool schemas up to date automatically

MCP (Model Context Protocol) tools added to an Agent node in Maestro Flow can drift out of date if the underlying MCP server's tool definition changes after you configure it — for example, a parameter gets renamed or added.

A new Refresh schema before call toggle, in the tool's configuration panel and on by default, checks the MCP server for the tool's current schema right before each call, so the workflow keeps working even if you never refresh it manually. When disabled, the tool always uses the schema you configured, which is faster and more predictable if the server's tools rarely change. The setting is saved with the workflow and survives closing and reopening the project.

詳細については、「 エージェント」をご覧ください。

Trigger ad-hoc case tasks through the CaseApp API

In Maestro Case, a new POST /instances/{instanceId}/tasks/trigger endpoint on the v3 CaseApp API lets you manually start an ad-hoc task on a running case instance by supplying its case-plan task name. Access requires the Cases.RunAdhocTasks permission scoped to the stage that owns the task. Task name matching is case-sensitive, and only tasks with an "adhoc" entry condition in the case plan are eligible — other names return a 404.

For more information, see CaseApp requests.

バグ修正

• Maestro BPMN: =js: expressions used as Data Fabric query filter values are now evaluated before the query is sent, so dynamic values resolve correctly instead of being passed through as raw expression strings. For more information, see Data Fabric operations.
• Maestro BPMN: The Get queue items activity no longer fails on Orchestrator tenants with the Strict OData API setting enabled. For more information, see Queue task activities.
• Maestro BPMN: Multi-instance elements with large marker input collections no longer fail during execution. For more information, see Markers.
• Maestro BPMN: A Studio Web debug run against an empty queue now returns a 404 (user error) instead of a 500 (system error); deployed runs are unaffected.
• Maestro Flow: Evaluation output evaluators (such as Exact Match) are now pre-selected and pre-filled with the shared expected output entered in the evaluation wizard. For more information, see Evaluations.
• Maestro Flow: The MCP server picker in the add-node panel now loads all available servers instead of stopping at the first 100. For more information, see Agent.