Connect apps

Zyx speaks MCP, the open standard AI tools use to call tools. A connected app’s MCP server becomes ordinary tools inside Zyx, behind the same kernel and the same cards. Zyx is an MCP client toward your apps, and an MCP server toward your AI tools (see Use Zyx from your AI tool).

The catalog

The Connections screen shows one card per app. Today there are 63 apps you can connect, 33 of them with one-click sign-in. A further 6 cards are marked “coming soon”.

Kind of card	How many	What it takes	Examples
One-click sign-in (MCP with OAuth)	33	press Connect and sign in to the app	Stripe, Linear, Notion, Slack, Jira, Canva, Miro, Asana, Box, Sentry, Supabase, Vercel
Token	8	paste the app’s key	Airtable, HubSpot, Firecrawl, Google Workspace, Resend
No credential	8	nothing, or a local setting	Figma (desktop), Context7, Microsoft Learn, Lighthouse
Built in	14	part of Zyx	the browser, mail, GitHub, and the synced search sources

Each card is one file in the Zyx repository. A new app is a new file, not new code. Every card reads “not connected” until a live call against the company’s own account succeeds.

How a connection works

No connection row, no tools. A card alone adds nothing. Removing the connection removes its tools everywhere at once.
Per tool: off, read, or write. The owner picks which of an app’s tools Zyx may use.
Tools that send or pay always ask. If an app’s tool sends something out or moves money, every call is an approval card, even if the app lists it as a read.
Secrets stay in the secrets file. A key or token goes into Zyx’s encrypted secrets file on the server. The connector file stores only the secret’s name, never its value.
App results are data, not instructions. Every result from an app is marked as untrusted data. The model gets at most 20,000 characters of a result. A longer result is saved whole as a file in the chat’s folder, where Zyx reads the rest; a result that holds a key is not saved.
Files an app’s tool writes into the company folder, such as an export, are listed in the chat. A file that was already there keeps a copy first, so the change can be undone.
Files from an app (PDF, Office, images, text) are saved to the chat’s inbox folder after their type and size are checked: at most 10 files, 25 MB each, per result. A link to a file is never fetched.

When the app offers no self-registration

Some sign-in servers let no new app register itself (Asana and Box, for example). Their card asks once for the company’s own app: it shows the redirect address to register, and the owner pastes the app’s client id and secret.

Mail

The mail card takes several mailboxes over IMAP and SMTP, each with an app password. Zyx never asks for a password in the chat. Outlook and Microsoft 365 mailboxes cannot connect this way yet, because Microsoft accepts no app passwords there.

Proton Mail connects through Proton Mail Bridge, which runs on your own server. It needs Proton Mail Plus or higher. Pick the provider “proton bridge” and Zyx fills in the server settings; you paste the Bridge password and the certificate Bridge exports. Bridge must keep running while Zyx reads or sends mail. Only the owner sets this up, for the company: a staff member’s own mailbox cannot name a server on the Zyx server.

A staff member can sign in to a company app with their own account (Connections, Company apps), and connect their own mailbox or Notion key (Connections, My connections). What they connect answers only in their private chats. The owner sees “name - app - status” and nothing else. See Readers and rights.

What is not offered

Reading a LinkedIn feed or messages. There is no compliant way for a vendor of this size to do it.
Reading Slack direct messages or private channels the Slack app is not in.
Posting to Microsoft Teams, Discord and WhatsApp Business are not built.