Skip to main content
Connectors are external integrations that extend what an agent can do. When an agent needs a capability it doesn’t have built in — querying a database, reading an onchain oracle, calling an external API — it searches for a connector. The tool name for this is connectors_find.

Two origins

Connectors come from two sources:
  • MCP servers — Model Context Protocol servers that expose tools, resources, and prompts. These are standard integrations that any MCP-compatible client can use.
  • Onchain tools — Smart-contract-based integrations onchain. Examples include Chainlink price feeds, onchain data oracles, and contract reads/writes. The agent treats these like any other connector but routes the call through the chain.
The agent does not distinguish between the two at the event level — both surface as connectors_find events. The display metadata on the raw event tells you which origin a given connector came from.

Event shape

A parsed connector tool event has these fields:

Stream example

Display metadata

The display object includes a human-readable connector name and summary. Check display.kind to see the origin: