Set up a connector
Connect a provider app to your Cloud, decide which of its tools Emerge.ai may use without asking, and enable it in a chat.
What you'll do
A connector links a provider app — Gmail, Asana, Zoom — to your Cloud so Emerge.ai can work with what is in it. Setting one up has three parts: connect the app in Cloud Settings, decide what Emerge.ai may do with it, then enable it in the chat where you want it.
Slow down for the middle part. Several of a connector's tools can send, draft, or change things in the connected app, and you decide which of those Emerge.ai may do without checking with you first.
Connectors are managed per Cloud, in Cloud Settings → Connectors, and connecting signs in one account — the entry shows which as "Connected as" once it is linked.
Connectors are beta, so expect their behaviour to keep changing.
Step-by-step
- Open Cloud Settings → Connectors.
- Find the connector you want. Each entry shows its status, a description of what it lets Emerge.ai do, and a Connect button.
- Select Connect and complete sign-in with the provider.
- Review that connector's Available tools under Tool permissions, and decide for each tool that acts on your behalf whether it is Always allow or Ask each time.
- Enable the connector in the chat where you want to use it. Connecting the app does not by itself put it to work in a conversation.
What a connector's entry shows
Until it has been set up, a connector's status reads Not connected — the app is not linked and none of its tools are in play. It is not an error, and not a connection that failed.
Each entry's description says what that connector is for. Gmail's reads: "Connect Gmail so Emerge can help search messages, summarize email context, and draft responses when you enable the connector in chat." Its Key features add search by sender, subject, and content; email context in chat responses; and access "scoped to the connected user account" — the one account you connected, not everything the provider holds.
Choosing what Emerge.ai is allowed to do
The Tool permissions section puts its purpose plainly: "Review when Emerge is allowed to use connector tools."
Every connector exposes a set of Available tools — the individual actions it can perform in the connected app. Reading and acting are not treated the same:
- Tools that only read are always allowed and carry no setting to change.
- Tools that change something — sending an email, posting a message, changing a record in the connected app — ask you first by default. Each of these carries a switch between Ask each time and Always allow, so you decide which actions Emerge.ai may take without checking with you.
A Set all control applies one setting across a connector's tools that carry the choice. It cuts both ways: using it to put a connector entirely on Always allow also removes the prompt from the acting tools that default to asking.
Set all covers one connector's tools, not every connector — changing it for Gmail says nothing about Asana.
Which tools a connector exposes differs from one connector to the next. The list for any connector is the one shown under it in Cloud Settings, and What you can connect is this site's checked copy of it.
Enabling a connector in a chat
Connecting an app and using it are two separate steps. Connecting makes the app available to the Cloud; enabling it in a conversation is what puts it to work there. In chat, the Connect Apps control lists the connected apps, each with a per-chat toggle.
Adding a custom connector
Not every tool a team uses is on Emerge.ai's list. Add Custom MCP opens a panel to "Set up a custom connector to a remote MCP server", which Emerge.ai then treats as a connector alongside the rest. Two fields do the work: Name (placeholder: "Linear MCP, Internal tools, …") and Remote MCP server URL (placeholder: "https://example.com/mcp").
An Advanced settings group holds optional OAuth details, needed in one circumstance only, which the panel states: "These fields are only used when the MCP server does not expose OAuth metadata automatically." Leave it alone unless the server requires it, and get the values from whoever runs that server.
Definitions
- Connector — a link between a provider app and a Cloud, letting Emerge.ai work with what is in that app through the tools you allow.
- Available tools — the individual actions a connector can perform in the connected app. The set differs from one connector to the next.
- Always allow / Ask each time — the two settings carried by tools that act on your behalf: usable without asking, or only after you approve it.
- Set all — a control that applies one setting across a single connector's tools that carry the choice.
- Custom connector — a connector you add yourself with Add Custom MCP, pointing at a remote MCP server instead of an app Emerge.ai already lists.
Related topics
- Connectors overview — what a connector is, and the connectors available
- Platform & Apps — the surfaces Emerge.ai runs on
- Invite your team — adding people, agents, and apps to a chat
- Troubleshooting
What you can connect
The provider apps Emerge.ai connects to, the named tools each one exposes, and which connectors can only read — with Cloud Settings named as the live source, because Emerge.ai adds connectors over time.
Custom MCP
Pointing Emerge.ai at a remote MCP server so it appears as a connector alongside the built-in ones, what the panel needs, and what stays your responsibility once it is connected.
