The September 2025 update of Flow is mainly a service release, focused on internal improvements to prepare for upcoming releases centered on debugging and developer experience. Still, we’ve added a few new features, including package installation to folders and OAuth support for Flow MCP servers.
Install packages to folders
You can now install Packages into folders, making it easier to manage and organize Packages from other sources. To do this, select a folder in the Workspace Explorer, open the Installed Packages tab, and click Install.
Updated Workspace Objects UI
We updated the Workspace Objects UI to make it quicker to find and edit connections when there are many. The UI now looks more like the toolbox, making the UI more uniform and familiar.
Flow MCP servers now support OAuth
Flow MCP servers now support OAuth authentication, the official protocol recommended in the MCP specification. This allows MCP clients to authenticate and connect to Flow MCP servers using a standard protocol, utilizing dynamic client registration if the identity provider supports it.
By default, Microsoft Entra ID is used as the authorization server, but you can also configure your own, such as Keycloak, Auth0, or Okta.
Read more about MCP Server Settings here.
Markdown conversion enhancements
We’ve released an improved version of our document conversion service for turning various file formats into Markdown. It now scales dynamically to handle heavier loads and processes conversions faster.
Bug fixes and minor enhancements
- Fixed issue related to pgVector for PostgreSQL vector db operations
- The Run Flow action (for nested execution) now supports conversion of custom data types returned from the called Flow
- If you try to open a Flow in a Workspace that you don’t have access to, you now get an unauthorized message instead of a generic error message
- You can now use use variables to specify which field to filter on when doing vector search
- The supported formats list of the Adobe nodes that converts from non-PDF to PDF files
- Cached InVision objects are now immediately evicted from the cache when the Remove InVision object from cache action is used.