About connectors

A connector is how an external source or service — GitHub, Postgres, Google Drive, Slack, Stripe, and hundreds more — becomes reachable from inside a connect0 project. You connect it once; from then on every agent on the project acts through the same governed link instead of juggling its own tokens.

A connector is a project-scoped instance

When you connect something, connect0 stores a connector instance scoped to one project. It lives under the project (/a/<account>/p/<project>/connections), is audited like everything else, and is invisible to other projects. Two projects that both talk to GitHub each hold their own instance with their own credentials — there is no account-wide shared connection that leaks across workspaces.

Because the instance is the unit of scoping, granting an agent access to a source is a per-agent, per-connection decision. An agent can only use a connection you have explicitly granted it (see Create an agent).

Auth is handled for you

You never paste raw API keys into agent code. connect0 runs the OAuth handshake or stores the API key for you, wraps the secret at rest, and resolves it at call time. For an OAuth provider you complete the provider's consent screen once through connect0; for an API-key provider you supply the key once. Refresh and re-auth are handled behind the link — when a grant expires, the next call surfaces a re-auth prompt rather than failing silently.

Two ways a connector is used

• Materialised into the workspace (read). A data source like a GitHub repo or a Postgres schema is pulled read-only into /workspace/connectors/<mount_prefix>/, where the mount_prefix you chose names the folder. Agents read it with plain sh. See Connect a data source.
• Invoked as an action (read/write). A service like Slack or Stripe is called through the connection when a skill or tool needs it — the connection resolves the credential and dispatches the call.

Every call, in either shape, lands an audit row scoped to the project.

Where to go next

• Connect a data source to register your first connector and materialise it.
• The public MCP server to drive connectors from an external MCP client with the connector.* tools.