Connectors

Connect a service once and make its tools available to selected local chats or agents. A connector is separate from the engine’s own sign-in.

Add from the catalog

1. Open Settings › Connectors and browse the directory.
2. Choose a preset such as GitHub, Sentry, Cloudflare, Linear, or Notion. Follow the entry’s authentication instructions: some use browser sign-in, some need a token, and public documentation servers may need neither.
3. Connect and check the reported tool count or error.
4. Choose All chats or Specific agents, then set the write policy. Ask an allowed chat to use the service.

Gmail

Gmail is marked Early access and uses Google sign-in through Shelzo’s bundled Gmail helper. Availability depends on the app’s Google OAuth configuration. If the build reports missing configuration or Google does not allow your account, the connector cannot complete sign-in. Your engine’s login does not grant Gmail access.

Add an MCP server

MCP is the protocol connectors use to offer tools. Choose Add connector, then HTTP for a server URL or Command for a local server process. Enter the URL or command and arguments, then the required authentication headers or environment variables. Credential values are stored in Keychain.

The CLI import section can read supported existing CLI connector configurations. Review the imported entry and any duplicate status before connecting.

Write policies

• Ask each time: a write tool waits for a decision in the chat or Inbox.
• Allow: write tools run without another connector approval.
• Never: write tools are denied; read tools remain available.

For example, allow a documentation search while requiring approval before a service changes a record. Read-only classification comes from the server’s tool metadata. Computer uses the label Off for its input-blocking policy; see Computer use.

If it fails

Read the inline connection error and connector activity. Check that the connector is enabled and granted to this chat or agent. Use Sign in again for expired authentication. For a command server, verify the executable and required environment variables; for HTTP, verify the URL and authentication. App connectors are not forwarded into SSH chats.