---
sourceDocument: Yokohama Enable AI
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/intelligent-experiences

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# MCP Server with OAuth 2.1

# Add an MCP Server with OAuth 2.1 {#ariaid-title1}

Release version: Yokohama  
Updated July 2, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Add an MCP Server with OAuth 2.1 in the AI Agent Studio.

## Before you begin

Role required: sn_mcp_client.admin

## About this task

OAuth is the recommended method to authenticate the MCP servers. If your MCP server supports it, choose OAuth 2.1 in the Authentication method.

## Procedure

1. Navigate to AllAI Agent StudioSettings.
2. Navigate to Manage MCP Servers and select New.
3. On the form, fill in the fields.  
   {#add-an-oauth-2-1-mcp-server__table_jnr_n3g_xfc__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name for your MCP Server. |
   | Authentication Type | The authentication type with which you want to add your MCP Server. Select OAuth 2.1. |
   | MCP Server URL | The web address of your MCP Server. |
   [Table 1. Add MCP Server]

   {#add-an-oauth-2-1-mcp-server__table_jnr_n3g_xfc}

4. Select Next.  
   The form extends with the registration details.
5. On the form, fill in the fields:  
   The dynamic client registration auto-populates the data in the form fields.  
   Note:  
   If dynamic registration is supported by the MCP Server, you will be prompted to confirm the grant type and other inputs. If dynamic registration is not supported, you can continue with the Manual Registration method in Step 6.
   {#add-an-oauth-2-1-mcp-server__table_zcx_vq3_xfc__entry__2}

   | Field | Description |
   |-|-|
   | Grant Type | The way you want to obtain an access token for accessing protected resources. One of the following two options is used here with auto-populated data. * Authorization Code: A system-generated code that is used for granting access to an application or resource. * Client Credentials: Access token provided by the administrator to access the application directly. {#add-an-oauth-2-1-mcp-server__ul_adx_vq3_xfc} |
   | Token Authentication Method | Unique token granted to access resources. Select the value from the drop-down list. |
   | Auth Scopes | Define the specific permissions for an application. Note: The Auth scopes must be comma-separated values. |
   | Authentication Token for Client Registration | Authentication token used to verify client's identity and grant it permission to register with an authorization token. Provide the following values: * Header: Authorization header. * Value: Authentication password. {#add-an-oauth-2-1-mcp-server__ul_bdx_vq3_xfc} |
   | Authorization URL | Web address of your server to direct authorization. |
   | Token URL | Web address containing the token. |
   | Token Revocation URL | Web address to revoke the previously provided token. |
   [Table 2. Dynamic Client Registration]

   {#add-an-oauth-2-1-mcp-server__table_zcx_vq3_xfc}

   The MCP Server with dynamic client registration is added as a simple connection and credential alias.
6. On the form, fill in the fields:  
   Note:  
   * If your MCP Server doesn't support Dynamic Client Registration, then you can register the OAuth client for AI agents in your MCP Server manually and update those client details in AI Agent Studio.
   * The manual client registration doesn't auto-populate the data in the form fields and must be manually provided.
   * 
   {#add-an-oauth-2-1-mcp-server__ul_rt1_qzl_bgc}
   {#add-an-oauth-2-1-mcp-server__table_yds_tsh_xfc__entry__2}

   | Field | Description |
   |-|-|
   | Grant Type | The way you want to obtain an access token for accessing protected resources. You can select one of the two options: * Authorization Code: A system-generated code that is used for grating access to an application or resource. * Client Credentials: Access token provided by the administrator to access the application directly. {#add-an-oauth-2-1-mcp-server__ul_epg_223_xfc} |
   | Token Authentication Method | Unique token granted to access resources. Select the value from the drop-down list. |
   | Client ID | Unique ID for authentication and authorization purposes. |
   | Client Secret | Unique credentials used for authentication. |
   | Auth Scopes | Define the specific permissions for an application. Note: The Auth scopes must be comma-separated values. |
   | Authentication Token for Client Registration | Authentication token used to verify client's identity and grant it permission to register with an authorization token. Provide the following values: * Header: Authorization header. * Value: Authentication password. {#add-an-oauth-2-1-mcp-server__ul_spy_cj3_xfc} |
   | Authorization URL | Web address of your server to direct authorization. |
   | Token URL | Web address containing the token. |
   | Token Revocation URL | Web address to revoke the previously provided token. |
   [Table 3. Manual Registration]

   {#add-an-oauth-2-1-mcp-server__table_yds_tsh_xfc}

   {#add-an-oauth-2-1-mcp-server__manual-registration}
{#add-an-oauth-2-1-mcp-server__manual-registration}
7. Select Add.  
   The MCP Server with OAuth 2.1 gets added and appears in the list of MCP servers.
8. Open the OAuth MCP Server record and select Authenticate.  
   Note:  
   When the OAuth access or refresh tokens aren't available, you must authenticate the OAuth configuration on the MCP Server record to add it as a tool to an AI agent.

*[\>]: and then