Skip to main content

connectors — Connectors

External MCP servers and OpenAPI integrations the agent can call (Notion, Stripe, Bitly, Google, …). Each connector contributes tools at chat time. Section key connectors · Shape object · Tier All plans
Edit in the dashboard: Connectors page
Related: Connectors guide

Fields

connectors items

List of active MCP/tool connectors.

connectors.event_handlers items

Per-connector MCP event handlers. Each handler matches inbound MCP events by name (and optionally by a payload-filter JSONPath) and either runs sandboxed code, invokes a built-in tool, or fires off an agent run. See project_mcp_event_handlers.

connectors.event_handlers.event_match fields

Which inbound event(s) this handler fires for.

connectors.event_handlers.handler fields

What to do when the handler matches.

connectors.event_handlers.pipeline fields

Unified incoming-event pipeline for this event (pre-processor → interpreters → classifier → context → notes). When present it supersedes the legacy ‘handler’ action. The event_match/payload_filter above remain the selector. See $lib/shared/event-pipeline.

connectors.event_handlers.pipeline.preProcessor fields

connectors.event_handlers.pipeline.interpreters items

connectors.event_handlers.pipeline.classifier fields

connectors.event_handlers.pipeline.outputContract fields

Optional post-LLM output contract: parse the agent reply as JSON and (optionally) validate it against schema; enforced on MCP connector events. See $lib/shared/event-pipeline OutputContractConfig.