Connections
Authorize services, MCP servers, and browser sessions for Atoi to use.
A connection lets Atoi read or act in a service you authorized, within the scope that service granted. Connect one when Atoi needs your GitHub, Google Workspace, Linear, or Slack account to do the work.
#See what is connected
Open Settings → Plugins. That tab holds your Connections. Connect GitHub, Google Workspace, Linear, or Slack. You can also add a remote MCP server, a channel, or a browser session you captured.
| Status | Meaning |
|---|---|
| Connected | Atoi can use it now |
| Limited | Some of the expected scope is missing |
| Needs attention | There is an error or a recovery step |
| Not connected | Nothing authorized yet |
Open the detail page to see the scope and the last error. Connected does not mean every repository, board, or document. It means exactly what you granted.
#Connect a service
Choose the service and follow its sign-in flow. You return to the detail page when it is done. Never paste a key into a thread. Enter it on the provider page, where Atoi masks it after you save.
For an MCP server, enter its endpoint and authorization. For a browser session, sign in through the controlled browser window. Atoi stores the session in an encrypted vault and notes every use in the thread.
From the terminal:
atoi connector list --json
atoi connector connect github
#Least authority
Connect only what the work needs. Atoi prefers an API over a browser and a browser over a desktop. Even with a healthy connection, consequential writes still show an approval.
#Fix or revoke
When a connection needs attention, read the error before you reconnect. Reconnecting can change the scope. Revoke a connection when Atoi should stop using it. Receipts from when it was valid stay in their threads.
Read MCP clients to give a coding client access, or Channels to continue a thread somewhere else.
Was this useful?