Connections

A Connection authorizes Atoi to use an external service, MCP server, channel destination, or captured browser session within the scope that provider granted.

#Browse current connections

Open Connections to see available rows and their current product state. The web model includes first-party presentations for GitHub, Google Workspace, Linear, and Slack, plus remote MCP, channel, and captured-session records where configured.

Read the detail page for scope and recovery. A connected badge does not promise access to every repository, workspace, document, or browser account.

#Connect through the supported flow

Use the product’s provider flow rather than pasting a secret into chat. OAuth and account authorization should return to the Connection detail. API keys remain masked secret inputs.

For a remote MCP server, enter the endpoint and authorization through its governed setup surface. For a captured browser session, complete login in the controlled browser flow and treat the resulting session as sensitive account access.

#Use least authority

Connect only the service and scope required for the outcome. Atoi should prefer a native API or MCP capability before browser or desktop control. Consequential writes can still require an approval even when the Connection is healthy.

#Recover or revoke

When a row needs attention, inspect the current error before reconnecting. Reauthorization can change provider scope. Revoke a Connection when Atoi should no longer use it; this does not automatically delete historical receipts created while it was valid.

[!NOTE] Human-facing copy uses Connection. The machine-facing CLI command remains atoi connector where that spelling is part of the stable command contract.