TIBCO Flogo® (formerly known as TIBCO Flogo® Enterprise) enables AI orchestration and intelligent automation through a visual flow designer integrated into Visual Studio Code. Built on a high-performance Go (Golang) engine, it delivers superior runtime efficiency, an ultra-light memory footprint, fast startup, and low-latency processing across edge, cloud, serverless, and on-premises environments. With its AI-ready architecture and powerful set of connectors, Flogo® transforms enterprise data into intelligent, event-driven, AI-ready workflows. To understand all the capabilities, see Build Event-driven Apps with an Ultralight Framework.

What's new in version 2.26.5 (June 2026)

• Upgrade Google Connection to Override Service Account Key: You can securely configure Google connections by leveraging enhanced options for the Service Account Key. You can override the key using a Base64-encoded value, a JSON service account key, a file path (starting with file://), or a Kubernetes secret, providing greater flexibility in managing your Google connections. For more information, see TIBCO Flogo® Connectors User Guide.

• TIBCO Flogo® Connector for Agentic AI - Tech Preview:

  • Azure OpenAI LLM Provider support: A new AzureOpenAI provider option in the LLM Provider Configuration enables direct integration with Azure-hosted OpenAI models using Azure-specific deployment, region, and resource settings.

  • Memory Conversation Store in the LLM Client Activity: The LLM Client Activity now supports an in-process memory conversation store, enabling multi-turn conversational interactions.

  • Dynamic MCP Server and A2A Server configuration via LLM Client Activity inputs: The LLM Client Activity Input tab now includes mcpServerConfigs and a2aServerConfigs array fields, allowing MCP servers and A2A remote agents to be configured dynamically at runtime without pre-configured connection resources.

• TIBCO Flogo® Connector for Model Context Protocol (MCP):

  • Scope-based access control for JWT authentication: A new Required Scope field on MCP Server handlers enables per-tool, per-prompt, and per-resource authorization based on JWT token scopes.

  • Structured content support for tool responses: A new Reply Settings tab with Tool Output Schema and a structuredContent field in Map from Flow Outputs enable MCP tools to return structured, schema-validated responses alongside text responses.

  • Content annotations for tool responses: The MCP Server trigger reply now includes optional audience and priority fields on the tool response object, enabling MCP content annotations on tool results. For existing apps, you must sync the trigger reply schema to pick up the new audience and priority fields before they can be mapped in the flow.

  • Enhanced tokenInfo claims: The tokenInfo object in Map to Flow Inputs now exposes additional standard JWT claims (iss, sub, aud, name, email) for richer authorization and audit logging.

  • MCP Client Activity: A new activity that enables Flogo flows to invoke tools on remote MCP servers as an MCP client, with support for multiple transport types, authentication modes, and structured JSON responses.

  • MCP Client OAuth2 Configuration: A new connection type that provides OAuth2 authentication for the MCP Client Activity, supporting both Client Credentials and Authorization Code grant types.

  • OpenTelemetry support for MCP Server trigger: The MCP Server trigger now supports OpenTelemetry for distributed tracing and observability of MCP server operations.

• TIBCO Flogo® Connector for Apache Pulsar:

  • Trigger-level Flowlimit: TIBCO Flogo® Connector for Apache Pulsar now supports trigger-level flowlimit.

For complete release details, see TIBCO Flogo® 2.26.5 Release Notes.