Managing Integrations
Last Modified: 2026-11-19

Managing Integrations

The Integrations page controls how AI applications and scripts connect to Agent ID to read its data. All access granted through this page is read-only: no connected application or key can change Agent ID data.

The page has two sections, grouped under AI and API access:

  • Agent ID MCP server: Lets AI applications, such as Claude or ChatGPT, read Agent ID data. A person signs in and approves access for each application.
  • API keys: Lets scripts and headless agents read Agent ID data when no one is signed in.

Each card summarizes the section's current state, for example 2 applications connected or No active keys. Select a card, or its Manage link, to open it.

To read data from the sources that Agent ID discovers from, such as AWS or Microsoft Entra ID, use Connectors instead. For more information, see Connecting Discovery Data Sources.

Note: The MCP server and API keys require a license that includes AI access. If your license does not include it, both cards display Not licensed and cannot be opened. Contact your RSA account team to enable them.

Choose the option that matches how the data will be accessed:

Option

Use it for

How access is granted

Agent ID MCP serverAI applications that people use, such as Claude, Claude Code, Cursor, or ChatGPTEach person signs in and approves access. The application sees what that person can see.
API keysScripts, integrations, and headless agents that run with no one signed inAn administrator creates a key that expires after a set period.

Connecting AI Applications through the Agent ID MCP Server

Each tenant has its own MCP server URL. Add the URL to an AI application as a remote MCP server or connector. The first time a person connects, they sign in to Agent ID and approve the application's read-only access. After that, the application can read the Agent ID data that the person is allowed to see. Each person approves an application once.

The Agent ID MCP server page contains:

  • Connect an AI application: the tenant's MCP server URL, with a Copy button, and a How this works section that summarizes the three steps: add the URL, sign in and approve, then read data.
  • Connected applications: the applications that people have approved.
  • A link to Manage API keys, shown with the number of active keys, for headless agents and scripts.

Connecting an Application

Procedure

  1. Go to Settings > Integrations and select Agent ID MCP server.
  2. Next to MCP server URL, select Copy.
  3. In the AI application, add the URL as a remote MCP server or connector. The steps depend on the application; see its documentation.
  4. When the application prompts for access, sign in to Agent ID. Review the request on the AI application access page, then select Allow access.

    The request shows the Application name, your Tenant, and the account you are Signed in as. Under Access, it shows Read Agent ID data and confirms that the application cannot change Agent ID data. To see the address that the application returns to and how it registered, expand Technical details.

Results

A confirmation page shows that the application is connected and can read Agent ID data using your account. Return to the application to continue. The application appears in Connected applications with the status Active and a New badge.

If you select Deny instead, the application isn't connected and the page shows Access denied. You can close the window.

Note: Only approve an application that you just tried to connect. If you didn't start a connection, select Deny.

Reviewing Connected Applications

The Connected applications table lists every application that a person has approved, including applications whose access was later revoked.

Column

Description

ApplicationThe name of the AI application
Approved byThe person who approved the application's access
AddedThe date that access was approved
Last usedWhen the application last accessed Agent ID
Status

Active: The application can read Agent ID data.

Revoked: Access was withdrawn. The column also shows the date and the administrator who revoked it.

ActionsA menu with View details and, for active applications, Revoke access

Procedure

  1. On the Agent ID MCP server page, select an application row, or select Actions > View details.
  2. Review the application's Overview panel.

    • Connection details: Access (Read Agent ID data), Approved by, Added, and Last used. For a revoked application, it also shows Revoked with the date and administrator.
    • Technical details: Returns to (where the application receives its sign-in response, for example claude.ai or 127.0.0.1 (this computer)), Registration (for example, Registered itself on first connection), and Client ID.

If no application has connected, the table is replaced by No AI applications connected. Add the MCP server URL to an AI application to get started.

Revoking an Application's Access

Revoke access when you no longer need an application, when the person who approved it has left your organization, or when someone approved it in error.

Procedure

  1. On the Agent ID MCP server page, in the application's row, select Actions > Revoke access. You can also open the application's details panel and select Actions > Revoke access.
  2. In the Revoke access for <application>? dialog, review the person who approved the access and the date, then select Revoke access.

Results

The application loses access to Agent ID with this authorization, and its status changes to Revoked. To reconnect, a person must approve the application again.

Resolving Connection Errors

If a connection fails, the person connecting sees one of the following messages.

Message

Where it appears

What to do

Authorization failed

Agent ID could not confirm the sign-in, so the application was not connected.

The Agent ID authorization pageTry again from the AI application. If the error continues, contact your administrator and provide the Reference and Time shown under Technical details.

Agent ID MCP server can't be reached

The AI applicationCheck that the URL in the application matches the MCP server URL in Settings > Integrations, then try again. The authorization page provides an Open Integrations button.

This connection can't be completed

Agent ID did not recognize the application, so no access was granted.

The Agent ID authorization pageRemove the connection in the AI application, add the MCP server URL again, and retry. If the error continues, provide the Reference shown under Technical details to your administrator.

Using API Keys

An API key gives a script, integration, or headless agent read-only access to Agent ID when no one is signed in. People who use AI applications do not need a key; they connect through the Agent ID MCP server instead. The API keys page includes an Open MCP server link for this reason.

The API keys table lists every key in the tenant.

Column

Description

KeyThe key's name and the first characters of the key (for example, rsa_pak_VZKd…), which help you identify it. The full key is shown only once, when it is created.
CreatedWhen the key was created, and the administrator who created it
ExpiresWhen the key stops working, for example In 89 days
Last usedWhen the key last accessed Agent ID, or Never
Status

Active: The key works.

Rotated: A replacement key was created, and this key keeps working until the time shown (for example, Stops working in 23 h).

Revoked: The key was withdrawn and no longer works. The column shows the date and administrator, or notes that it was rotated.

Expired: The key reached its expiry date and no longer works.

ActionsA menu with Rotate key and Revoke key for active keys, and Revoke key for rotated keys. Revoked and expired keys have no actions.

Creating an API Key

Procedure

  1. Go to Settings > Integrations > API keys and select Create key.
  2. In Name, enter what will use the key (for example, SOC weekly report). A name is required.
  3. Under Expires after, select 30 days, 90 days, 180 days, or 365 days.
  4. Select Create key.
  5. Select Copy next to the API key and store it securely, for example, in a secrets manager.

    Note: Agent ID shows the full key only once. After you close the dialog, you can't display the key again and must create a new one. If you select Done without copying the key, Agent ID asks you to confirm before it closes the dialog.

  6. (Optional) Under Use this key, select how you will use the key to display example settings:

    • REST API: An example request for scripts and integrations, using the header Authorization: Bearer <key>
    • MCP client: The MCP server URL and the Authorization header for headless agents and automated MCP clients

    Replace <key> with the key you copied.

  7. Select Done.

Results

The key appears at the top of the API keys table with the status Active.

Note: Keys are read-only. A key cannot change Agent ID data.

Rotating an API Key

Rotate a key before it expires, or if you suspect that it was exposed. Rotating creates a replacement key with the same name and the same expiry period as the original, so you can update your script without downtime.

Procedure

  1. In the key's row, select Actions > Rotate key.
  2. Under Old key stops working, select when the old key stops:

    • After 24 hours (default): gives you time to update everything that uses the old key.
    • Immediately: anything that uses the old key fails until it is updated.
  3. Select Rotate key.
  4. Copy the new key as described in the procedure for creating an API key, then select Done.
  5. Update the script or integration to use the new key.

Results

The new key appears in the table as Active. If you chose Immediately, the old key's status changes to Revoked. If you chose After 24 hours, the old key's status changes to Rotated and the table shows when it stops working.

Revoking an API Key

Revoke a key to stop it working right away, for example when it is no longer needed or has been exposed.

Procedure

  1. In the key's row, select Actions > Revoke key.
  2. In the Revoke <key name>? dialog, select Revoke key.

Results

The key stops working immediately, and any script or integration that uses it fails until it is given a new key. The key's status changes to Revoked.

Note: Revoking a key cannot be undone. To restore access, create a new key.