Accessibility Adjustments

Use these optional tools to adjust reading and display preferences. These tools cannot resolve every accessibility barrier. Please contact the website owner if you need assistance.

  • Text adjustments
  • Content scaling 100%
  • Font size 100%
  • Line height 100%
  • Letter spacing 100%
  • Colour adjustments
  • Orientation adjustments

Activepieces 0.93.0 updates MCP setup and agent integrations

Listen to this article

Activepieces published version 0.93.0 on November 8, 2026. Its release notes include MCP client OAuth2 support, setup guidance for five additional AI clients and expanded agent integrations. For teams connecting assistants to business workflows, the practical change is a wider choice of connections and tools.

The release gathers changes to the platform and its separately versioned integrations. Installing a new server version does not automatically update the integration versions already used by existing workflows. The notes include tools for working with Letta agents, organizing Mem notes and filling PDF forms.

What MCP OAuth2 changes

The MCP client update addresses a specific connection problem. Some MCP servers require OAuth2 authentication without giving users a client ID and secret to enter manually. The implementation adds authentication discovery and OAuth2 connection support to the MCP Client integration.

According to the implementation description, users only need to supply the server URL when the remaining connection information can be discovered. Connecting then opens an authentication popup before tools can be discovered and called.

That implementation was merged on October 18. Version 0.93.0 is the newly published release containing it, so the release date should not be read as the first appearance of every individual feature.

Five more clients get setup guidance

A change merged on November 8 adds setup pages for Copilot CLI, goose, Cline, Zed and Antigravity. It also updates Windsurf’s presentation to Devin, with configuration file guidance covering its desktop app and CLI.

Client recognition has limits. Copilot CLI must register the expected pair of callback addresses to be identified. An ambiguous local callback shared by Zed and newer OpenCode remains labeled MCP client, rather than being incorrectly identified as Claude Code. The pull request specifically notes that Zed’s tile does not show Connected.

Users should therefore check the actual connection and test a tool call rather than treating a tile label as definitive proof that an assistant is connected or disconnected. For the separate terminal and editor workflow, our Copilot CLI settings guide explains GitHub’s recent configuration changes.

Two directions of connection

Activepieces supports both directions of an MCP connection. The OAuth2 client change lets Activepieces connect to external MCP servers. Its own built in server lets an external assistant work with Activepieces.

The MCP server documentation describes enabling that server in settings, copying its URL and authenticating from a compatible client. Available functions include inspecting failed runs, building flows and managing tables. Discovery tools remain available, while other tool categories can be controlled per project.

An assistant that needs to inspect an automation does not necessarily need permission to publish flows or modify records. Start with the categories required for the task. Activepieces says MCP tools are free except ap_run_action, which costs one credit per call. Flow runs started by tools are billed normally.

What existing users should check

Activepieces’ piece versioning documentation says official integrations synchronize separately, subject to compatibility with the running server. Existing flow steps stay pinned to their chosen integration versions until someone explicitly changes them in the builder.

That creates two upgrade questions. Does the server support the integration version you want? And is the relevant flow step actually using it? The builder’s version selector, rather than the server’s release number alone, answers the second question.

For installations managed with Docker Compose, the deployment guide warns that the container image is pinned to a release. Administrators need to update that selection when upgrading and review the documented breaking changes.

Before changing a production workflow, identify one connection or action that the update makes useful, select its supported version and test the expected output with sample data. ByteForward reviewed the published sources for this article and has not independently tested version 0.93.0.

Featured image: AI generated editorial illustration, not a product interface. Activepieces logo used for editorial identification. No endorsement implied.

Jordan Reid
Jordan Reid

Jordan Reid is focused on AI tools, agents, developer products, and the way technology changes everyday work. Jordan approaches a launch from the user’s side of the screen. What can it actually help someone finish? The voice is practical, conversational, and skeptical of products that turn a simple job into five new settings. Coverage follows coding assistants, creative software, browser agents, and the workflows around them, with attention to pricing, permissions, setup, and the human work that remains.

Leave a Reply

Your email address will not be published. Required fields are marked *

Gravatar profile