Paperclip enables four MCP aggregators while retaining provider choice

Paperclip has removed the experimental gate from four existing MCP aggregator connections. The September 24 merge makes their setup available without an instance-wide opt-in, including on installations whose old setting was false. Alongside it, a separate merged routing change keeps native integrations first and gives users an explicit choice when an external provider is needed. The news is the product default and decision flow, not four newly invented integrations or a blanket claim that every supported app has been exercised.

The facts

- PR #13964 merged September 24 and names Zapier, Arcade, Composio Connect and Executor as default-on providers. - Saved and managed values of the retired experimental setting remain parseable but no longer disable those providers. - Companion PR #13941 prefers a native connection and otherwise ranks verified external alternatives. - The routing contract preserves a None choice and checks saved human selection rather than treating an agent query as consent. - The acceptance document records real-agent proof for three providers, but not a completed Zapier tool call. - The rollout retains account authorization, agent access and tool policies; removing the catalog switch does not grant them.

Why it matters

A connector catalog can blur three different states: an integration is visible, an account is connected, and an agent is authorized to perform a particular action. Paperclip is trying to keep those distinctions visible while reducing setup friction. Its routing evidence also distinguishes a provider account from access to the underlying app. For operators, this matters more than the size of the catalog: a ready gateway is not proof that a particular account can read Jira, change a spreadsheet or execute a selected tool.

Current

Both changes are merged source as of September 25. The inspected stable release baseline remains v2026.916.1, published before these merges; this brief does not assert that every packaged or hosted installation contains them. The older routing proposal still mentions an experimental gate, but the later default-on change explicitly removes it. The September 24 acceptance addendum preserves, rather than erases, the earlier live-test limits.

Evidence

Primary: paperclipai/paperclip PR #13964 (https://github.com/paperclipai/paperclip/pull/13964). Supporting context: paperclipai/paperclip PR #13941 (https://github.com/paperclipai/paperclip/pull/13941); paperclipai — REMOTE-MCP-LIVE-ACCEPTANCE.md (https://raw.githubusercontent.com/paperclipai/paperclip/8d53c58ac8a76b60207ce236ca555e5c98ead800/doc/connections/REMOTE-MCP-LIVE-ACCEPTANCE.md). Source pages and available diffs were inspected; test and live-account results remain attributed to their authors, not independently repeated measurements.

Operator take

Treat this as a reason to review connector discovery and consent screens when the change reaches your deployment. Confirm that a native route wins where available, that declining an external provider stops setup, and that reconnecting an account does not broaden saved agent access. The project's targeted browser cases used a real agent against a deterministic MCP fixture for routing; they are useful workflow evidence but not a substitute for a real call against your selected app. Start with a harmless read and inspect the resulting audit record before extending permissions.

Caveat

Zapier's historical live acceptance remains incomplete. The maintainer requested the default-on rollout as a scoped exception, not as proof of the missing result. Reported focused tests and CI were not rerun here; availability on an installed release still requires checking that deployment.