Skip to content
Before you create the Connection
Public Preview

Create and manage an MCP Connection

Create an MCP Connection to let Agent Identities use a remote server's Tools, then manage authentication, assignments, and access.

This guide covers prerequisites, remote identity, creation and verification, and access management for MCP Connections.

  • Required permissions and prerequisites.
  • Remote account identity and environment separation.
  • Connection creation, authentication, and catalog verification.
  • Changing assignments and stopping access.

Summaries were generated by AI.

Create an MCP Connection so the Agent Identities you choose can use a remote server’s Tools. You can reuse the Connection across your organization.

When you assign a Connection to an Agent Identity, that Agent Identity can use every compatible Tool that the server offers, now or later, as Review a changing MCP catalog explains. Review the whole catalog before you allow calls. If a person must approve an action, Secure integration states where to put that approval for an MCP Tool.

Before you create the Connection

You need:

  • These permissions in the selected Tenant (Identity explains them):
    • config:read_config and config:create_config on config:*, to use the Dashboard creation flow.
    • tools:read_catalog on tenant:<tenant_id>, to see the catalog.
    • agent:manage_tools on each agent:<agent_id> you assign.
  • A multi-factor sign-in (aal2). Sign-in levels defines each level.
  • A public HTTPS MCP endpoint that uses Streamable HTTP and answers at the exact configured URL, without a redirect. The Tools reference lists the URL rules and the supported protocol versions.
  • A server catalog within the MCP catalog limits.

Know which identity reaches the server

The configured bearer token or API key identifies the remote account. Every Agent Identity assigned to one Connection acts with that account and its remote permissions, so give the account only the access its Tools need.

Create a separate Connection and remote account for each environment or data set, such as CRM Production and CRM Sandbox, and for each team that needs its own remote permissions.

Create and verify the Connection

  1. Open Tools

    In the Dashboard, select your Tenant, open Tools, then choose Create Connection.

  2. Describe the remote server

    Enter a Connection name that names the system and its environment, such as CRM Production. The model reads this name with the Connection’s Tools. Then enter the public HTTPS endpoint.

  3. Choose remote authentication

    Select No authentication, Bearer token, or API key. A bearer token is sent as Authorization: Bearer <token>. For an API key, enter the header name your server expects; Choose one authentication mode states which names Duale AI refuses. Saved secret values are not shown again. Replace a value to rotate it.

  4. Enable the Connection and set Tool access

    Keep the Connection enabled, and under Tool access select allow or block. Connection policy states what each choice does.

  5. Save and inspect the catalog

    Save the Connection. The Dashboard opens its detail page. Wait until the catalog shows Active, as Catalog freshness describes; the Tool catalog section then shows the Tools the server reported.

  6. Assign Agent Identities

    On the Connection detail page, choose Manage assignments, select the Agent Identities, then choose Save assignments.

After the catalog becomes Active, submit a test Task under an assigned Agent Identity. In its instruction, ask for an operation that one of the Connection’s Tools serves, preferably one that only reads data. Open the Task in the Task view to see the Tool Call and its outcome. For a Tool that changes data, also confirm the change in the destination system. If the catalog does not become Active, follow Troubleshoot Tools.

Operate Tools explains catalog states, model-facing names, and Analytics.

Change or stop access

Each change requires its own access:

  • Editing the Connection requires config:update_config on config:*.
  • Changing an assignment requires agent:manage_tools on that agent:<agent_id>.
  • Deleting the Connection requires config:delete_config on config:* and an aal3 sign-in.

To stop calls but keep the saved configuration, set Tool access to block or disable the Connection. To end access for one Agent Identity, choose Remove beside it under Agent Identity assignments on the Connection detail page. To end access for every Agent Identity and remove the configuration, delete the Connection.

Changes apply shortly after you save and do not cancel a remote call that already started. Connection policy compares blocking with disabling and states how a later call ends after each change.