Skip to content
AtoiDocumentation
Use Atoi

Connections

Authorize services, MCP servers, and browser sessions for Atoi to use.

Open in Atoi
You authorize a service, the service grants a scope, and Atoi acts inside that scope only01Yousign in once02The servicegrants the scopeWhat Atoi may doread what you grantedact inside that scopenothing widerOutside the grantAtoi says so instead of guessinga key is never pasted into a threadConnected, usable nowLimited, scope is missingNeeds attention, read the errorNot connected, nothing grantedEach connection reads as one statusa healthy connection still meets the gate
Connected names the grant, not the whole account. Outside it, Atoi says so.

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 → Connections. Your connections are listed there, one row each, by kind: accounts, apps, messaging, and MCP servers. Connect GitHub, Google Workspace, Linear, or Slack from its row. The same page adds a remote MCP server or a messaging link, and lists the browser sessions you captured. A Mac or another computer you paired lives under Computers, with its tokens and context sync.

StatusMeaning
ConnectedAtoi can use it now
LimitedSome of the expected scope is missing
Needs attentionThere is an error or a recovery step
Not connectedNothing 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:

bash
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 Messaging to continue a thread somewhere else.

Was this useful?