Skip to content

Integrations / repository capability matrix

Start at the boundary you own.

Pipedream → LangChain → Nango → Mastra. This is the adoption order, with local support and remaining work shown separately for each platform.

Local support, with its limits.

All packages are unpublished. These are implementation and fixture boundaries, not installed partner integrations, production coverage or a live availability feed.

Local proxy adapter / offline fixture

Pipedream →

Supported locally
Wrap client.proxy with clientAdapter in your Node runtime. The offline fixture exercises the actual proxy client with a synthetic local transport.
Planned
Partner publication and hosted/provider qualification remain pending.
Unsupported / unqualified
Wrapping a container does not discover nested clients. Auth and storage helpers are outside the guard; hidden provider calls are not inspected.
Local invoke adapter / offline ToolCall fixture

LangChain →

Supported locally
toolAdapter preserves name, description and schema and guards the actual invoke / ToolCall executor, retaining tool IDs and execution configuration.
Planned
Broader LangGraph and framework batch/stream qualification remains pending.
Unsupported / unqualified
The invoke adapter does not qualify batch/stream paths. Class ToolMessage response replacement is unavailable; original outcomes survive with a bypass.
Local A/B adapters / limited C codegen

Nango →

Supported locally
Surface A: clientAdapter on HTTP proxy methods. Surface B: bounded JSON in a customer Node proxy script through httpAdapter. Surface C: zero-dependency codegen for supported action/sync exec bodies; only explicitly confirmed same-type request sibling renames may repair.
Planned
Hosted snapshot delivery, runtime opt-out delivery, partner adoption and deployed Nango qualification remain pending.
Unsupported / unqualified
No npm in the action/sync sandbox. Never guard batchSave, getCheckpoint or saveCheckpoint. Codegen has no statistics, learned invariants, automatic conversions, hosted audit or write-integrity proof; arrays, deep paths and incomplete captures are unavailable.
Local execute-shape fixture / framework adoption planned

Mastra →

Supported locally
toolAdapter accepts execute definitions while retaining id, description, inputSchema identity and execution context. Current evidence is a local shape fixture, not full framework execution.
Planned
Full framework integration, middleware qualification and distribution remain planned. Review the ee/ license boundary before vendoring.
Unsupported / unqualified
A generic execute wrapper does not establish middleware, batch/stream or hosted Mastra support.

Other boundaries

AI SDK

Local execute-shape support preserves schema metadata. Full framework and batch/stream coverage is unqualified; its own repairToolCall does not establish AGINDOW verification.

Current adapter guide ↗

Composio / Merge / Paragon

Unsupported inside closed catalogs: the SDK cannot reach hidden executors. Customer agent-layer wrapping requires an accessible callable. An observe-only MCP integration remains planned; no hosted MCP delivery is claimed.

Boundary and alternatives ↗

HTTP and Python

Node Fetch/Express adapters inspect only supported bounded JSON. Python supports local decorators and an explicit remote fail-open API; Python framework adapters are unavailable.

Node HTTP constraints ↗Python guide ↗