Crates

Generated by connectors-docs from cargo metadata --no-deps: every package of the workspace, with the description its Cargo.toml gives. There are 23 packages. None is on a registry; build them from the source checkout. The generated CLI parser, apps/connectors-cli-contract, is a path dependency of connectors outside the workspace and is regenerated by connectors-build cli, never edited.

Libraries and the command line

The shared boundary an application, an adapter or a host builds on, and the connectors command.

Package	Directory	In Rust	What it is
connectors	apps/connectors	use connectors, binary connectors	The connectors command: invoke a connector's operations, and set up instances, connections and approvals through a local owner.
connectors-catalog	crates/connectors-catalog	use connectors_catalog	Catalog ingest: a pinned OpenAPI source document compiled into a bundle with the provenance every later artifact cites; never reaches the network.
connectors-client	crates/connectors-client	use connectors_client	Generic client that describes an adapter service and invokes its operations over the service wire.
connectors-contracts	crates/connectors-contracts	use connectors_contracts	Higher-level, provider-neutral data and discovery contracts.
connectors-core	crates/connectors-core	use connectors_core	Provider-independent operation and service wire contracts: descriptors, requests, results, errors and limits.
connectors-custody	crates/connectors-custody	use connectors_custody	Credential custody of the local host: the read and write backend traits, an in-memory reference, one platform binding each for the Secret Service, the macOS login keychain and the Windows Credential Manager, and the explicitly selected read-only mounted-secret binding on Linux.
connectors-definitions-install	crates/connectors-definitions-install	use connectors_definitions_install	Fetches a connectors-definitions release by tag from an https repository or a local directory, checks every file against its index.json, and records it in a lock file and a read-only cache keyed by the index's SHA-256; depends on no connectors crate and embeds no catalog.
connectors-host	crates/connectors-host	use connectors_host	Adapter service host: HTTP serving, credential references, one-hop federation, and the local owner, custody and metadata runtime.
connectors-oauth2	crates/connectors-oauth2	use connectors_oauth2	Provider-neutral OAuth 2.0 client: the authorization-code grant with PKCE, the device grant, the code and refresh exchanges and the loopback and pasted-code redirect receivers, over a transport the host supplies.
connectors-sdk	crates/connectors-sdk	use connectors_sdk	The adapter interface and shared semantic mechanisms (descriptors, handler verification, cursors); concrete infrastructure stays with the host.
connectors-spec	crates/connectors-spec	use connectors_spec	The adapter specification kind: compiles adapter specifications to descriptors and pins the ESS release used for generation.
connectors-tool-contracts	crates/connectors-tool-contracts	use connectors_tool_contracts, binary connectors-tool-contracts	Publishes an instance's tool-contract/1 document from its descriptor and the tool profiles authored beside its adapter, and serves it as a tool-conformance/1 toolset over the adapter's invoke.

Adapters

Each adapter owns its provider behaviour and builds a standalone executable. With --no-default-features the library alone depends on no host, client or sibling adapter; the repository gate holds that boundary.

Package	Directory	In Rust	What it is
connectors-catalog-provider	adapters/catalog	use connectors_catalog_provider, binary connectors-catalog-provider	The catalog provider: one verified bundle, a declarative selection of its operations, and one engine that binds, sends and classifies them.
connectors-grafana	adapters/grafana	use connectors_grafana, binary connectors-grafana	Grafana adapter: bounded data-source records from the Grafana HTTP API, and read-only IRM alert groups, incidents and their links over a since window.
connectors-kubernetes	adapters/kubernetes	use connectors_kubernetes, binary connectors-kubernetes	Kubernetes adapter: resource inventory, endpoint and host discovery, and Helm release reads.
connectors-loki	adapters/loki	use connectors_loki, binary connectors-loki	Loki adapter: LogQL range and metric queries and label reads, one GET each.
connectors-mcp	adapters/mcp/runtime	use connectors_mcp	Native MCP mechanics of the stdio server: launch grammar, newline framing, tool names, exact JSON, results, the local lease and request supervision; admission and custody are ports the application supplies.
connectors-prometheus	adapters/prometheus	use connectors_prometheus, binary connectors-prometheus	Prometheus adapter: PromQL instant and range queries and the rule list, one GET each.
connectors-sql	adapters/sql	use connectors_sql, binary connectors-sql	SQL adapter (PostgreSQL and MySQL): bounded read-only queries, catalogue reads (databases, tables, columns and keys, indexes) and configured read profiles with typed, masked, keyset-paged output.
connectors-tavily	adapters/tavily	use connectors_tavily, binary connectors-tavily	Tavily adapter: web search, page fetch and site crawl through the shared websearch family.

Repository tooling

Generators, checks and acceptance runners the repository's own gate and maintainers use. Nothing outside the repository depends on them.

Package	Directory	In Rust	What it is
connectors-build	crates/connectors-build	binary connectors-build	Repository build tool: the gate, generation and drift checks, catalog bundles, source projections and the website examples.
connectors-conformance	crates/connectors-conformance	binary connectors-conformance	Live acceptance runner against independently started adapter services.
connectors-docs	crates/connectors-docs	binary connectors-docs	Generates the derived pages of the Connectors documentation site (CLI, crates, contract and model reference, status) and checks them for drift.