Connection overview

Connections bring source material into ctx| so agents can use it as organization-scoped context. ctx| is Git-first: GitHub gives ctx| access to code, while context repositories provide a transparent home for selected content from other systems.

That means your team keeps control. You choose what ctx| can read, where synced content lands, and what becomes part of the knowledge system agents can query.

GitHub is the foundation

Most teams start by connecting GitHub. This lets ctx| read selected repositories, build code search, and ingest repository structure into your organization's knowledge system.

GitHub is critical because it supports two jobs:

• It gives ctx| direct access to source code for single-repo and cross-repo code search.
• It provides the target repositories used by other connections, such as Confluence, Slack, Linear, and Notion, when external content needs to become repo-backed context.

Three source behaviors

Do not treat every connection as the same kind of synchronization:

• Git sources — GitHub repositories are indexed directly.
• Scoped mirrors — Linear, Notion, and Confluence write approved source scope to Git, then keep that selected content current.
• Intent capture — Slack writes one existing thread only when a user mentions the bot inside it. There is no channel mirror or history backfill.

The Git-backed paths give your team:

• A visible Git history for synced context.
• A clear repo owner and review surface.
• One ingestion path for code, docs, and synced source material.
• Better control over what agents can rely on.

Agents use ctx| through MCP

MCP is agent access, not another source connection. Agents connect to ctx| once, then ask for context from the sources your organization has connected, indexed, and ingested.

For setup details, see ctx| MCP.