There is nothing to connect — whatever you meet or call with.
Thalassa listens to the sound on your own computer, so the application makes no difference: Zoom, Teams, Meet, Webex, GoTo, RingCentral, Whereby, Proton Meet, Jitsi, Slack, Discord, WhatsApp, Telegram, Signal, Messenger, FaceTime, Viber, LINE, KakaoTalk, WeChat, Zalo — or a phone on speaker.
It does not join your meeting, it is not a participant, and it asks your meeting platform for nothing. Whatever you use — a conferencing service, a team chat, a messenger, a phone on speaker — there is nothing to set up, no admin approval to chase and no IT ticket to raise. The names above are examples, not a list of integrations: there is no integration to have.
Optional connections to your own systems — where they really stand
These pull in your own documents and context. Each is listed with the status it actually has — a connection we have not finished is named as unfinished, never implied.
Status as of 13 September 2026.
| System | Connection | Reading & writing data |
|---|---|---|
| MCP tool providers | Available now | Yes — tool by tool, after your confirmation |
| Google Workspace | Sign-in works | Reading your data: not yet |
| Microsoft 365 / Outlook | Prepared | Not yet |
| Salesforce | Prepared | In progress |
| HubSpot | Prepared | Not yet |
| Clio Manage | Prepared | Not yet |
| iManage Work | Prepared, set up per firm | Not yet |
“Prepared” means the sign-in path works and the place the credential is kept has been tested. What is missing is registration with that provider for production use, and the part that actually fetches the data. None of this is needed to run a meeting.
If a system you rely on is missing, tell us through the contact form.
MCP: connect tool providers
Any system that offers an MCP endpoint can be connected today — document and matter management, compliance, CRM and sales, management tools, and your own internal or AI systems. You are no longer waiting for a separate integration per system: one connector, and every provider with an MCP endpoint is within reach. Included in every plan, alongside the six connections above. Add a tool provider in the desktop app's settings, load its catalog and choose the tools available to the assistant.
Supported providers expose tools through MCP Streamable HTTP. The assistant can propose tool calls for answers and briefings. Before each call, the app or overlay shows the provider, tool and exact inputs for your confirmation. Tools may read or change information, depending on the provider. Text and structured results are supported; local stdio servers, OAuth discovery and binary results are not. The existing text-resource import remains available separately.
Connections you configure yourself; data goes to the destination you choose. The desktop app connects directly to your chosen server. Retrieved text is indexed and searched on your device. Selected excerpts used in answers and briefings follow the existing request path through Thalassa's backend and the configured model service, with the source shown. See the privacy policy.