DPRO · OPEN SOURCE · MIT · VERSION 0.2.0
Agent Connect
Connect your agents and applications through one reusable TypeScript interface: 33 bundled integrations for messengers, email, webhooks, APIs and relay connections.
33 bundled integrations
Telegram and Discord run natively in Node.js. The other adapters need an optional, isolated Python environment and provider configuration.
A2APython adapter
API ServerPython adapter
iMessage via BlueBubblesPython adapter
BuzzPython adapter
DingTalkPython adapter
DiscordNative · Node.js
EmailPython adapter
Feishu / LarkPython adapter
Google ChatPython adapter
Home AssistantPython adapter
IRCPython adapter
LINEPython adapter
MatrixPython adapter
MattermostPython adapter
Microsoft Graph WebhookPython adapter
ntfyPython adapter
iMessage via PhotonPython adapter
QQ BotPython adapter
RaftPython adapter
Connector RelayPython adapter
SignalPython adapter
SimpleX ChatPython adapter
SlackPython adapter
SMS (Twilio)Python adapter
Microsoft TeamsPython adapter
TelegramNative · Node.js
WebhookPython adapter
WeCom (Enterprise WeChat)Python adapter
WeCom Callback (self-built apps)Python adapter
WeixinPython adapter
WhatsAppPython adapter
WhatsApp Cloud APIPython adapter
YuanbaoPython adapter
One interface for every channel.
Agent Connect is a framework-independent Node.js library with shared connection lifecycle, incoming-message callbacks and provider-acknowledged outbound text delivery. Integrate it with your own backend, identity checks and agent runtime.
Telegram uses long polling. Discord supports guild text channels. Your application handles sender authorization, storage, rate limits and model execution.
Install and integrate
Requires a persistent Node.js 22.12+ process. The package uses ESM and includes TypeScript declarations; short-lived serverless functions are unsuitable for its connections.
npm install agent-connect-dproRelease scope
Version 0.2.0 is published on npm. Registry installation of the initial 0.1.0 release was verified. Live bot/model validation remains pending.
The library does not include a frontend, HTTP server or model. Frontend screens and HTTP endpoints belong to separate Agent Player integrations. Bot credentials stay in your server configuration.