Activepieces’ November 8, 2026 release adds a sign-in option that could unblock some business automations. Operations teams and small-business owners can now configure its MCP Client to connect to external tool servers that require OAuth—the familiar process of signing in and granting an application access.
Whether a particular connection will work still depends on the external provider. The important question is whether it can register Activepieces as a connecting application in a supported way, automatically or manually. A service advertising OAuth support is not enough to establish compatibility.
What changes for your workflow
MCP, short for Model Context Protocol, is a standard way for software to connect to tools. Here, the direction matters: an Activepieces flow calls a tool hosted elsewhere. This is different from Activepieces’ built-in MCP server, which lets an outside AI assistant work with Activepieces itself.
The earlier released connection options included tokens, API keys and custom headers, but no built-in OAuth sign-in. The new authentication definition adds OAuth while retaining those options. If a provider-supported token connection already works, this addition alone is no reason to replace it.
An AI model does not have to choose the action. Activepieces describes the MCP Client as calling tools without a language model; its Call Tool action runs the named tool with the supplied inputs. The practical benefit is access to more protected services for a predefined workflow, not a new AI decision-maker.
Choose the setup your provider supports
Automatic setup needs the provider’s sign-in details and a way to register the connecting application. The released discovery code also requires a client secret: a credential issued for that application, separate from the person’s password.
What the provider offers | What to do |
|---|---|
Discoverable sign-in details and automatic registration that returns a client secret using a supported authentication method. | Try automatic setup. Select OAuth2, enter the server address and its supported connection type, then choose Connect. The connection definition describes discovery and registration before sign-in. |
No usable automatic setup, but supported manual application registration. | Ask the provider for its client ID and secret, authorization and token addresses, required permissions and redirect requirements. The connection form exposes manual fields after a discovery-specific failure. |
Only public clients that do not use a client secret. | The automatic registration path rejects these. Manual fields do not solve the problem unless the provider offers a supported registration with a secret. Ask about that option or use another documented connector. |
For manual registration, use the Redirect URL displayed in the Activepieces connection dialog when configuring the provider. Enter credentials only in the protected connection fields. Do not invent a client secret to fill a required box.
The decision is therefore narrower than “does this service support MCP?” Confirm its registration method first, then check the permissions and tool you actually need. Successful sign-in alone does not establish that the intended task works.
Check the version in the flow
Activepieces’ product page advertises OAuth support on cloud and self-hosted deployments, with the MCP Client included on every plan. That is not confirmation that each existing installation or flow has acquired it.
Release 0.93.0 contains MCP Client version 0.0.8. Activepieces documents that flow steps stay pinned to an exact component version until someone changes it. Its catalogue also filters components by server compatibility. If OAuth2 is missing, check the installed server, available connector version and version selected in the flow.
Use the final HTTPS server address. The breaking-change guidance says MCP Client 0.0.8 no longer follows endpoint redirects to another host or port. For a private-network server, an administrator should also check reachability and the documented outbound-network rules.
Plan inclusion is not unlimited usage
As of November 8, the pricing page lists MCP access on Free, alongside a 1,000-credit monthly allowance. It also contains conflicting daily and monthly wording about when Free credits reset. Confirm the account’s actual limit and replenishment timing before relying on it for scheduled work.
The Usage page shows plan credit limits and separates flow-run usage from AI usage. Budget for any external service separately, and for AI steps if the wider workflow uses them. The connector’s inclusion does not establish an all-in price for your task.
Confirm the action, not just the connection
The Call Tool implementation notes that remote tools may create or change data on each call. Selecting a fixed tool does not make a repeated call harmless, and OAuth consent is not approval of every future action. For more on that distinction, see our guide to Dropbox’s file-action approvals.
If OAuth was the missing piece in a blocked integration, revisit it with the provider’s registration details in hand. Before putting it into routine use, confirm the intended tool appears, its inputs and permissions fit the job, and a controlled trial produces the expected result. Otherwise, keep the working connection or defer the unsupported one.