ITWeb next release — Builder MCP (June 2026)
Status: Draft for Pash review → ITWeb submission (style pass, 20 Jul 2026)
Source: Kathy press release (US), SA-localized by Taylor
Recommended publication window: Early June 2026 (contract slot — April piece already ran)
Send to Pash by: Wednesday 4 June 2026 (allow 2–3 days for ITWeb processing)
Topic recommendation (for Taylor / Pash)
- **Builder MCP**: Recommended — use now — Kathy's final draft is in hand. Product is live on site; demo video available. Strong AI + governance angle for ITWeb enterprise readership.
- New runtime (SA): Defer to July — No Kathy runtime draft found in repo. Runtime messaging exists internally but timeliness is fading; still valid for July if US PR does not lead with it.
- Digital Executive podcast: Defer to July/Aug — No transcript or draft in repo. Daniel was strong on podcast — good spokesperson piece when materials are confirmed.
Decision: Proceed with Builder MCP for the imminent June slot. Kathy's US release can run on its own timeline; ITWeb version is SA-localized (dateline, enterprise context, POPIA-aware governance framing) without duplicating the same headline in the same week — coordinate send dates with Kathy (see alignment email).
Cover note for Pash (copy/paste)
Hi Pash — attached is the SA-localized ITWeb release for Builder MCP, edited from Kathy's US draft. Recommended hero: Builder MCP demo still from Daniel's YouTube demo (link below) or a product screenshot from the platform page — headshot only if ITWeb prefers a person-led image. Please submit to ITWeb for the June contract slot. Flag any claims you want Daniel/JJ to sign off on before submission. Taylor
Press release (ITWeb submission copy)
FOR IMMEDIATE RELEASE
Flowgear Launches Builder MCP to Bring Governed Integration Into AI Chats and IDEs
South African integration teams can scaffold and test Flowgear workflows from AI coding tools and local development environments - without opening a parallel, ungoverned stack.
JOHANNESBURG — 3 June 2026 — Flowgear, a South African-born Integration Development Environment used by more than 140 global partners and 1,000 certified developers worldwide, today announced Builder MCP: a Model Context Protocol (MCP) capability that lets technical teams build and test Flowgear workflows from an AI chat or local IDE, outside the Flowgear Console.
For integration architects and developers, that means scaffolding backend workflows from the tools they already use - Cursor, VS Code, Claude Desktop, and similar environments - without switching context or pasting credentials into a free-range agent.
Taming AI Sprawl in the Integration Layer
As AI-assisted coding moves into mainstream developer work, enterprises see a familiar risk in a new form: overlapping integrations, architectural drift, and security gaps when every team builds backend logic in isolation.
Builder MCP channels that work through validated patterns on Flowgear's infrastructure. The assistant gets a governed toolkit, not a blank canvas, so drafts can move toward production inside the same roles, connections, logs, and execution controls IT already relies on.
For South African enterprises navigating POPIA, segregation of duties, and ERP-centric operations, that matters: assistant-driven automation only scales when the underlying workflows stay inspectable, permissioned, and auditable.
Immediate operational benefits include:
- Build from anywhere. Create and test Flowgear workflows from external AI tools, IDEs, and local environments, using the same workflow-building surface available inside the Console.
- Shorter build-test loops. AI-assisted drafting reduces the gap between intent and a working workflow - so developers spend less time on boilerplate and context switching.
- Governance by default. Workflows built through Builder MCP inherit Flowgear's platform-level roles, connections, logs, and execution evidence - so nothing ships outside enterprise controls.
How Builder MCP Differs From Typical MCP Integrations
Many MCP implementations focus on giving AI agents access to existing apps, actions, or data sources. Flowgear Builder MCP goes further for integration teams: it lets them create and test new Flowgear workflows from outside the Console, using the same structured workflow model Flowgear's built-in tooling uses - and, where approved, expose selected workflows as MCP tools so assistants can call governed backend logic with clear input/output schemas.
That makes MCP useful for operational work - order status, inventory checks, finance exceptions, customer notifications - not only for retrieving static knowledge.
Short version: Builder MCP helps you build integrations from the tools you already use. Workflow MCP (where exposed) lets assistants use integrations you already approved.
"Builder MCP reimagines the integration lifecycle by embedding Flowgear's framework directly into the AI tools where engineering teams increasingly work," said Daniel Chilcott, co-founder and CEO of Flowgear. "By using AI to generate and refine structured backend logic safely, organisations can collapse integration backlogs and reach production readiness without the overhead of manual console-only design."
"Builder MCP gives enterprises the confidence to deploy AI-assisted automation because the underlying workflows are governed by a resilient, enterprise-grade environment," said JJ Milner, co-founder of Flowgear and founder and Managing Director of Global Micro Solutions. "AI development is only as good as the systems that surround it. With Builder MCP, we provide the structural foundation required to scale AI automation safely, reliably, and without sprawl."
Built for Connected Operations
Mid-market and enterprise organizations depend on dense webs of ERP, CRM, finance, logistics, and customer systems. When those systems stay disconnected, the cost shows up as manual handoffs, delayed visibility, and duplicated effort across business units.
Flowgear connects that estate with out-of-the-box infrastructure connectivity. With Builder MCP, technical teams can rapidly scaffold workflows that link, for example, online orders, stock levels, warehouse activity, ERP records, courier systems, and customer notifications - then adapt them as channels, fulfillment models, or logistics providers change.
Developers keep freedom to build in their preferred environments. Flowgear keeps credentials, approvals, and execution governed. Builder MCP extends that principle to AI-assisted workflow design.
To explore Builder MCP or register the endpoint with your AI agent, visit §LINK0§.
Demo video (for ITWeb embed or still capture): Builder MCP Demo by Daniel Chilcott
About Flowgear
Flowgear is an Integration Development Environment for building, running, and governing business integrations across cloud, hybrid, and on-premises systems. The platform combines a visual workflow designer, pre-built connectors, AI-assisted build experiences, Builder MCP, Workflow MCP, and observable runtime infrastructure so teams can integrate systems quickly while keeping control over credentials, approvals, and execution. Founded in South Africa in 2010 by Daniel Chilcott and JJ Milner, Flowgear supports customers and partners across multiple markets. For more information, visit flowgear.net.
Hero image recommendation
- **1. Builder MCP demo still** (from YouTube `RwQeZIr6FHQ`): Preferred — product-led, matches news angle — Grab a clean frame from Daniel's demo video; minimum 1200px wide if ITWeb specifies
- 2. Platform page screenshot: Alternative if video still is low resolution — Screenshot from
/platform/builder-mcponce site is live - 3. Daniel Chilcott headshot: Fallback if ITWeb requires a spokesperson image — Use approved PR headshot from last ITWeb piece (April)
Note for Pash: ITWeb typically accepts a single hero image with the release. Lead with product (option 1 or 2) unless the editor asks for a portrait.
Edit log (Kathy US → ITWeb SA)
- Dateline Atlanta → Johannesburg: ITWeb SA audience; SA-founded company
- Added POPIA / SA enterprise context: Local relevance without inventing customers
- Tightened "AI sprawl" section: ITWeb enterprise tone; less marketing repetition
- Clarified build vs expose MCP tools: Aligns with platform page (
platform-pages.ts) - Linked to `/platform/builder-mcp` and demo video: Actionable for readers; asset for hero still
- Removed redundant "Automation That Scales" subhead repetition: Press release length discipline
- 20 Jul 2026 library style pass: Cass register + Flowgear written CI: IDE lead, US English in body (quotes retained as approved), plain language, About rewritten off iPaaS / no-to-low-code
Claims retained from Kathy draft (already approved there): 140+ global partners; 1,000 certified developers; founded 2010. Confirm with Daniel/JJ if ITWeb requires fresh sign-off.
Quotes retained verbatim from Kathy-approved Daniel/JJ lines (including British spelling inside quote marks).
Not invented: No customer quotes, no new statistics, no named SA clients.
Open questions for client sign-off
- US vs SA timing: Can Kathy hold US wire until after ITWeb publishes (or vice versa) to avoid duplicate news same week?
- Product URL: Confirm
/platform/builder-mcpis live before submission — else useflowgear.nethomepage CTA. - JJ quote: Confirm JJ is comfortable with Global Micro Solutions attribution on ITWeb (same as US release).
- Runtime draft: Does Kathy have a separate runtime release, or should July ITWeb use internal messaging only?