Building a Multi-Connector Agent

Use this when an agent needs two or more Airbyte connectors.

Going from Single to Multi

The bootstrapping-agent skill shows the default single-connector pattern: AirbyteAuthConfig plus build_connector_tools. The builder's execute, inspect_connector, and read_skill_docs names are fixed, so the tool sets for more than one connector collide when registered on the same agent. Renaming the callables at registration avoids the collision, but the generated execute guidance still names inspect_connector and read_skill_docs, pointing the model at the wrong tools. Multi-connector agents write their own tool functions with @Connector.agent_tool(...), which weaves the real names in through inspect_tool= and docs_tool=:

1. Build a single AirbyteAuthConfig(...) so credentials are shared across connectors.
2. Construct one typed connector per service (e.g. JiraConnector(auth_config=auth)).
3. Define execute, inspect, and docs functions for each connector, each with its own @Connector.agent_tool(...) decorator.

Use connector-specific function names so the framework registers six unambiguous tools for two connectors.

Install the SDK

uv pip install airbyte-agent-sdk