Skip to main content

Your connectors

The Connectors screen lists the connectors available to you. Availability follows your group membership: an administrator grants a connector to groups, and you see it if you are in one of them.

If the list is empty, that is not a fault. It means no connector has been granted to your groups yet, and the screen says so. Ask an administrator rather than reconfiguring anything.

Enabling a connector​

Being able to see a connector and having it exposed to your tools are two different things. Enable the ones you want, and your MCP client sees those.

The reason for the extra step is tool volume: every enabled connector adds its tools to what your client has to choose between, and a client offered a hundred tools is measurably worse at picking the right one than a client offered ten. Enable what you are actually working with.

Your MCP gateway endpoint is shown at the top of the screen with a copy button, alongside a link to the setup instructions. Until you enable at least one connector, that endpoint has nothing to expose.

Signing in to a backend​

Some connectors reach a backend as you rather than as a shared service account. Those prompt you to sign in to that backend once, from this screen. After you do, the gateway holds the authorization and your later tool calls use it.

If a connector stops working and asks you to sign in again, that is the upstream authorization having expired or been revoked, which is expected occasionally rather than a fault.

Next steps​