Integrations & SDKs

The swarm speaks MCP natively, and a set of adapters carries it everywhere else.

ChatGPT

Data Workers ships as ChatGPT apps — an All-in-One app plus focused Catalog, Quality, and Incidents apps. Self-hosters can expose an agent to ChatGPT as a custom connector:

docker compose -f docker/docker-compose.chatgpt.yml up
# or expose one agent over HTTP:
DW_TRANSPORT=http DW_REMOTE_PORT=3001 npx tsx agents/dw-context-catalog/src/index.ts

Agent-to-agent (A2A)

The swarm implements the A2A protocol (spec 0.2.x) so external agent systems can discover and call it: Agent Card discovery, inbound message/send, and task status/cancel are shipped. A2A is opt-in and off by default — it only listens when you set DW_A2A_PORT. Streaming and outbound A2A are later, gated phases.

Framework adapters

For teams orchestrating their own agents:

• @data-workers/a2a-adapter — A2A server wrapper
• @data-workers/adk-adapter — Google ADK
• @data-workers/langchain-adapter — LangChain tools

Each wraps the same underlying agents, so capability and governance behavior is identical to the MCP surface.

Python SDK

A typed Python SDK (sync and async clients over the agents) is on the roadmap, not shipped. Until it lands, programmatic access is the MCP protocol itself — any MCP client library can call the agents — or the A2A surface above. Ask for it if it would unblock you; roadmap priority is demand-driven.

Build your own connector

The @data-workers/catalog-provider-sdk is the open interface our own catalog connectors implement — zero runtime dependencies, with a conformance kit to validate your implementation locally. It’s the supported path when your system doesn’t have a native connector.

VS Code

A VS Code extension ships in the repo (packages/vscode-extension) for teams whose engineers live outside the four first-class coding agents.