Overview

Jido Connect is the integration framework for host applications that need to expose provider tools to Jido agents. It defines the core connector contracts, catalog discovery surface, and safe tool-calling path used by provider apps such as GitHub, Slack, and MCP.

The repository is structured as an umbrella for development and publishing. Host applications should depend only on the provider packages they need, while the provider package brings in the shared jido_connect core dependency.

Purpose

Jido Connect provides a common boundary for provider integrations so agents can discover, describe, and invoke external tools without hard-coding every provider into the host application.

Boundary Lines

• Owns connector contracts, provider discovery, catalog search, and safe tool invocation.
• Owns provider slices for GitHub, Slack, and MCP while package boundaries are still settling.
• Does not own chat-channel adapters, long-term memory, or provider-specific business workflows outside connector operations.

Major Components

Core Contracts

Zoi-backed contracts under Jido.Connect define the shared integration surface and validation rules for connector providers.

DSL Extension

Spark DSL support gives provider authors a structured way to declare capabilities, actions, triggers, and provider metadata.

Provider Apps

Current provider slices include GitHub, Slack, and MCP apps for issue operations, message/file operations, and MCP tool bridging.

Catalog

Jido.Connect.Catalog discovers installed providers, searches tools deterministically, describes tool schemas, and routes safe execution through the connector invocation path.

Demo Host

A local Phoenix demo host exercises OAuth callbacks, GitHub App setup callbacks, webhooks, and provider routes without turning every provider package into a demo application.