Skip to content

Atoi documentation

Integrations


Connect the services, channels, and coding clients Atoi can work with.

Connections, Channels, and MCP clients enter one Thread01Connectionlinked service02Channeloutside conduit03MCP clientcoding clientThreadone conversationinputs stay visibleoutside inputs arrive without becoming separate homes
Connections, channels, and automations all arrive in the Thread you already use.

Guides

Use Integrations when Atoi should reach beyond the app: connect a service you authorize, continue a thread on Telegram or Slack, or give a coding client governed access to your projects.

Each path keeps its own status, errors, and receipts. A green badge or delivered message proves that one thing and nothing more.

Start with Connections, then Channels or MCP clients. Saved prompts on a schedule live under Automations.