Integration examples

Use the public package that owns each integration. MCP clients and A2A clients are exported by core; their server/transport adapters are exported by transport. There are no separate @agentium/mcp or @agentium/a2a workspace packages.

MCP tools

Use MCPToolProvider for SDK v1 compatibility or MCPV2ToolProvider for the split client SDK. Select tools, configure the Agent, and close the provider when its owner finishes. A bound tool list is a snapshot; rebuild it explicitly after server discovery changes. The MCP v2 guide includes a complete example with credential audience and cleanup. For legacy connections, see MCP examples.

Remote agents

Use A2ARemoteAgent, A2ARemoteTeam, and A2ARemoteWorkflow for the older protocol. Use A2A 1.0 for its explicit authenticated task ownership. Server task retention is process-local unless you select the durable bridge.

HTTP event destination

This example configures a webhook but does not run the Agent. Before using it, replace the destination with an application-owned endpoint and select events whose content you intend to send.

import { Agent, httpWebhook, openai } from "@agentium/core";

const agent = new Agent({
  name: "tracked-agent",
  model: openai(process.env.OPENAI_MODEL ?? "gpt-6.1-sol"),
  webhooks: {
    destinations: [httpWebhook({ url: "https://hooks.example.com/agent-events" })],
    events: ["run.complete", "run.error"],
    retries: 3,
  },
});
await agent.close();

slackWebhook and emailWebhook are destination factories, not classes. Configure them through the same webhooks.destinations array. See webhook configuration. Event destinations can transmit payloads; metadata-only observability capture does not redact an independently configured webhook.

HTTP and Socket.IO

Use Express or Socket.IO. Every text router/gateway selects local or authenticated mode explicitly. Hosted authorization checks the resource’s owner as well as the caller’s scopes. New session IDs must be atomically bound before execution.

Administration

@agentium/admin exports ConfigStore, EntityFactory, ToolkitManager, createAdminRouter, and createAdminGateway. The ordinary core Registry is a live runtime registry, not a persistent admin configuration store. Use the Admin Express guide, Admin Socket.IO guide, and configuration storage guide for their distinct lifecycles. Provider credentials, entity ownership, and application authorization remain host responsibilities.

Durable notifications and calls

For source-triggered notifications with persistent cursors and uncertain-send reconciliation, use durable watches. For outbound carrier call control, use telephony; connect its answer route to a voice/media runtime separately.

Complete projects

Agents & memory

Models & Jev

Tools & knowledge

Teams & jobs

Deploy & devices

Quality & production

Integration examples

MCP tools

Remote agents

HTTP event destination

HTTP and Socket.IO

Administration

Durable notifications and calls

​MCP tools

​Remote agents

​HTTP event destination

​HTTP and Socket.IO

​Administration

​Durable notifications and calls

MCP tools

Remote agents

HTTP event destination

HTTP and Socket.IO

Administration

Durable notifications and calls