Connector agents
Alongside unified MCP tools, each connected provider can expose a specialist agent over A2A (Agent-to-Agent)—a JSON-RPC endpoint plus a .well-known/agent.json card.
Use connector agents when an orchestrator should delegate a whole turn of reasoning about one integration (for example “triage open PagerDuty incidents”) instead of calling a single *_tool action.
What you get
| Artifact | Purpose |
|---|---|
| Agent card | {agent_base}/agents/{slug}/.well-known/agent.json — name, description, skills, capabilities |
| A2A endpoint | {agent_base}/agents/{slug}/a2a — JSON-RPC message/send (and streaming variants) |
| Skills chips | What the specialist is good at (shown in Tools & MCP → Agents) |
Active connectors with credentials appear in the Agents gallery. Manage providers under console Connectors.
MCP vs A2A
| MCP tools | A2A agents | |
|---|---|---|
| Granularity | One action per call | Full conversational turn |
| Best for | Deterministic CRUD / queries | Multi-step reasoning on one vendor |
| Client | Cursor, Claude, LangChain MCP adapters, … | Orchestrators that speak A2A / HTTP JSON-RPC |
Many production setups mix both: load unified MCP tools for broad access, and add an A2A tool that delegates to a specialist when needed. See Connect clients for framework examples.
Streaming chat for connector agents is also used by DevX Assist in the console. Tools & MCP is where you discover cards, endpoints, and copy-ready snippets.
Related
- Getting started — enable connectors first
- Platform tools — the MCP side of the same connectors
- Automation Studio — invoke agents and connector steps on a graph