Managing MCP Connections

Configure a per-user MCP Connection for a Remote MCP Server and verify that a connection authenticates successfully.

Assign an MCP Connection to an individual user account, or verify that a connection already configured on a Remote MCP Server authenticates successfully. To set the server's shared default connection instead, check Creating a remote MCP Server; for background on how default and per-user connections differ, check About MCP Connections.

Before you start

• The Remote MCP Server already exists.
• An Integration Service connection points at the same URL as the Remote MCP Server, and it's enabled.
• You have the following permissions in the folder that holds the server:
  • MCPServers.Edit, to manage connections for other users. This permission is part of folder roles such as Automation Developer and Folder Administrator.
  • Connections.Edit, to set or clear your own connection.

Configure a connection for a user account

1. On the MCP Servers page, open the actions menu on a Remote server row and select User configurations.

2. On the Connections per user account grid, select Add user configuration.

3. Choose the User account.

4. Select the Connection to use for that user.

   The picker lists connections that point at the server's URL and are either in a shared folder or in the selected user's own Personal Workspace. To view connections in another user's Personal Workspace, you need to explore that user's Personal Workspace first. If an expected connection is missing, its URL likely doesn't match the server's. The connection must also be enabled before you can assign it.

5. Select Save.

To change or remove a mapping, use the row actions in the grid. A row also appears automatically when a user with the Connections.Edit permission sets their own connection for the server, so the grid reflects both admin-assigned and self-service connections.

Verify a connection

1. Open the Remote MCP Server and refresh its tools.

   Orchestrator connects to the remote server and lists its tools, which only succeeds if authentication is accepted. If the tools load, the connection works.

2. If the MCP Inspector is available in your tenant, connect to the server there and invoke a tool to verify authentication end to end.

A failed connection usually surfaces as an authentication error from the remote server, or as a Requires authentication or Unavailable status on the Connections per user account page. For help resolving these, check Troubleshooting MCP Server authentication.