Use a Connector in chat

Choose the connectors a conversation uses and watch the model call their tools.

Agentic Friendly

Each conversation has its own set of Connectors switched on, and the model can call their tools while answering. An Agent can also bring its own Connectors, which are on from the start.

Turn a connector on or off

A new chat starts with every Connector you can reach switched on, so the model can call their tools from the first message. Turn off the ones a conversation should not use.

  1. Select Tools in the composer.
  2. Under Connectors, find the server. The list shows every Connector in your organization.
  3. Switch on the servers you want this conversation to use, and switch off the others.

Chat composer with the Tools popover open, Web search and the Context7 Connector switched on, Manage connectors at the bottom, and globe and server icons on the Tools button

Icons on the Tools button show what is on: a globe for web search, and a server icon, with a count when more than one Connector is on.

A server is yours to turn on once you can reach it: either you have linked your credential to it, or its credential mode is Unauthenticated and it needs no credential from anyone. An unauthenticated server is available to every member who may use it, with nothing to link first.

The choice belongs to the conversation, not to your account. A reopened chat keeps the Connectors it was saved with.

Build chats have the same Tools button, with the same defaults, Agent-required servers, and saved choices. A Connector's tools run in the platform, not in the Build sandbox.

Manage connectors at the bottom of the Tools popover opens the full list, which is where you link credentials and read what a server offers.

What you can and cannot turn on

The switch is unavailable in two cases, for opposite reasons.

StateSwitchWhy
You have not linked the serverOff, unavailableWithout your credential the server has nothing to act as. The row offers Link
The Agent requires the serverOn, unavailableThe Agent declares it, so the conversation always has it
Linked, not requiredYours to setThe ordinary case
Unauthenticated, not requiredYours to setThe server needs no credential, so nothing is missing

A row you have not linked shows Not linked and a Link action that takes you to the server. Link it, return, and the switch becomes available. An unauthenticated server never shows Not linked, because there is no link for it to be missing.

If your organization has no Connectors, the Tools popover lists none.

Agents that bring their own servers

An Agent can name the Connectors it needs. Those are on as soon as you pick the Agent, and marked Required by this Agent. You cannot turn them off because the Agent was built expecting them.

Requiring a server is not the same as giving you access to it. If you have not linked one the Agent needs, chat says so and the conversation runs without those tools rather than failing. An unauthenticated server the Agent requires raises no such notice, because there is no link for you to be missing.

Select Link now to fix it, then start the conversation again so the model has the tools from the first turn.

Watching the model use a tool

When the model decides a connector can answer something, the tool call and its result appear in the conversation before the reply that uses them.

Chat turn showing the model calling an MCP tool and the tool result above the assistant's answer

The model chooses whether to call a tool. Turning a connector on makes the tools available; it does not force their use. If the model answers without one, the connector was simply not needed.

The model only ever sees the tools the allowlist permits. A tool an administrator has not permitted is not offered and cannot be called, so the model behaves as though the server never had it. See Restrict which tools a Connector offers.

On a server where each user links their own credential, every call runs as you, with the credential you linked. Two people using the same connector in the same organization reach their own accounts on the upstream system, and see different results where their access differs. An unauthenticated server carries no identity to the upstream system, so nothing there distinguishes one member's call from another's. Your platform credential reaches neither kind.

On this page