Registering an AI Agent
Last Modified: 2026-11-19

Registering an AI Agent

The Agents registry is the record of every agent identity—discovered, registered, and enrolled—in one place.

Standard MCP clients register themselves the first time they connect to a gateway, so there is nothing to set up manually: the gateway sets up the matching application in your identity provider, and the agent appears in the console automatically.

Behind the scenes, an agent registers through a gateway registration endpoint that provisions the matching identity-provider client end to end: where the tenant's identity provider supports Dynamic Client Registration (DCR), the gateway uses DCR together with an Initial Access Token (IAT) and then issues the agent its own token. For identity providers without DCR support (for example, Microsoft Entra ID), the gateway uses an equivalent custom registration path behind the same registrar interface, so the registration experience is consistent regardless of which IdP a tenant uses.

Procedure 

  1. Point the agent's MCP client configuration at the gateway's MCP endpoint and run its connection/registration flow (for example, a coding assistant's Add MCP server step).
  2. Complete the registration/sign-in flow the gateway presents, so it can provision the agent's identity-provider client.
  3. On the Agents/NHI page, confirm the new agent appears with a status of Registered, then assign it an owner if it has none. For more information, see Managing Owners.

Results 

The agent's MCP client shows a connection status of connected and authenticated, with the number of tools it can see through the gateway, and the agent is now governed by whichever role the caller's identity-provider group maps to.