emerge.aiemerge.ai
Connectors

Connectors overview

What a connector is, which provider apps Emerge.ai connects to, and the guide for setting one up.

A connector links a provider app your team already uses — a mailbox, a calendar, a drive, a CRM — to a Cloud, so Emerge.ai can work with what is in that app. Each connector comes with its own set of tools, and you decide which of them Emerge.ai is allowed to use.

Connectors are managed per Cloud, in Cloud Settings → Connectors, and connecting signs in a specific account. Cloud Settings itself is the current list, so if a menu item is not where this page puts it, look for it there.

Connectors are beta — Gmail, Drive, Calendar, Microsoft 365, Asana and more — so expect their behaviour to keep changing.

What Emerge.ai connects to

What you can connect lists every connector, the tools each one brings, and which of them can only read. Emerge.ai adds to that set over time, so Cloud Settings → Connectors is the live list — check there for what you have today.

You can also add a connector of your own, by pointing Emerge.ai at a remote MCP (Model Context Protocol) server with Add Custom MCP.

Guides in this section

  • What you can connect — every connector, the tools each one exposes, and which connectors can only read.
  • Set up a connector — connecting a provider app, choosing which of its tools Emerge.ai may use without asking, enabling it in a chat, and adding a custom connector.
  • Custom MCP — pointing Emerge.ai at a remote MCP server, what the panel needs, and what stays your responsibility.

On this page