Skip to main content

1. MCP Client

Connect to an MCP server over stdio or HTTP and use its tools from a Agentium agent.
You can also connect over HTTP (SSE) for remote MCP servers:

2. MCP with Multiple Servers

Combine tools from several MCP servers into a single agent. Each server provides its own namespace of tools.

3. MCP Admin API

Manage MCP connections at runtime via REST. Add, remove, and list MCP servers dynamically.

4. A2A Server

Expose a Agentium agent as an A2A (Agent-to-Agent) endpoint so other agents or systems can call it.

5. A2A Client

Connect to a remote A2A agent and use it as a tool or team member in your local agent.

6. A2A Multi-Agent

Register multiple agents in a single A2A card so callers can discover and invoke any of them.

7. Webhook Events

Push agent events (run started, tool called, run completed) to an HTTP endpoint.

8. Slack Webhook

Send agent run summaries to a Slack channel via incoming webhook.

9. Email Notifications

Send error alerts via email when an agent run fails.

10. Queue Producer

Enqueue background agent jobs using BullMQ. Jobs are processed asynchronously by workers.

11. Queue Worker

Process background agent jobs with AgentWorker. Workers pull from the queue, run the agent, and store results.

12. Cron Scheduling

Schedule recurring agent runs using cron expressions. The agent runs automatically on the defined schedule.

13. Admin CRUD API

Dynamically create, update, and delete agents and teams at runtime via a REST admin API.

14. Admin Socket.IO

Real-time admin management via WebSocket. Create agents, run them, and stream results over Socket.IO.

15. Admin Storage

Persist admin-created agent blueprints to a database so they survive restarts.