---
title: "Flowgear v2 Update Adds v1 Workflow Calls and MCP Tools"
description: "Flowgear’s June 2026 v2 update lets teams call v1 workflows from v2, adds step-by-step debugging, and expands MCP setup and Builder MCP tools."
canonical_url: "https://liners.com/news/flowgear-v2-update-call-v1-workflows-mcp-tools"
markdown_url: "https://liners.com/news/flowgear-v2-update-call-v1-workflows-mcp-tools.md"
type: "article"
language: "en"
published_at: "2026-06-16T16:08:18.254Z"
updated_at: "2026-06-16T16:08:27.662Z"
---

# Flowgear v2 Update Adds v1 Workflow Calls and MCP Tools

Flowgear’s June 2026 v2 update lets teams call v1 workflows from v2, adds step-by-step debugging, and expands MCP setup and Builder MCP tools.

## Breadcrumbs

- [News](/news)
- [Flowgear v2 Update Adds v1 Workflow Calls and MCP Tools](/news/flowgear-v2-update-call-v1-workflows-mcp-tools)

## Content

## In Short
- Flowgear released a June 2026 update focused on making its v2 platform easier to adopt for day-to-day workflow development.
- The headline change is v2 support for calling v1 workflows directly, so teams can migrate gradually.
- Flowgear also added more precise workflow debugging, plus new MCP setup and Builder MCP tooling.

## What Happened
[Flowgear](/flowgear) says users can now call v1 workflows directly from v2 using a “Sub Workflow” step. A workflow is a set of automated steps that move data between apps, like a recipe that runs every time an event happens. This update means teams can start building new automations in v2 without rebuilding older v1 integrations first.

Flowgear also updated its workflow build and troubleshooting tools. Developers can now run a single step, run a workflow up to a specific step, and check recent activity logs for an individual step. This is meant to reduce time spent diagnosing issues in longer, more complex automations.

The company also added a dedicated MCP tab in the console. MCP, short for Model Context Protocol, is a way for AI agents to connect to tools and run tasks with clearer permissions and structure, like a standard plug that lets an assistant “operate” software safely. Flowgear says the MCP tab makes setup clearer and faster.

Finally, Flowgear expanded Builder MCP with tools that let agents review workflow logs and access workflow designs for v1 workflows.

## Why It Matters
Many businesses avoid platform upgrades because rewrites are expensive and risky. Letting v2 call v1 workflows supports a phased migration, so teams can modernise without pausing core integrations.

The step-level debugging features also point to a broader trend in automation tooling. As workflows get bigger and more connected across ERP, CRM, and support systems, operators need tighter visibility into what failed, where, and why.

Flowgear’s MCP additions suggest it expects more users to run workflows through AI assistants. If that pattern holds, tooling that makes setup, logs, and access controls easier will matter as much as adding new connectors.

## Sources and products

- [Flowgear](https://www.flowgear.net/start-in-v2-without-rebuilding-v1-june-2026)
- [Flowgear](/flowgear)

## Related pages

- [Product Launches](/news)

## Access and citation

- [Canonical HTML page](https://liners.com/news/flowgear-v2-update-call-v1-workflows-mcp-tools)
- [Markdown route index](/sitemap.md)
- [Agent access guide](/llms.txt)