---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Create an OAuth inbound integration for an MCP client

# Create an OAuth inbound integration for an MCP client {#ariaid-title1}

Release version: Australia  
Updated November 12, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Secure access to Model Context Protocol (MCP) servers on an instance by creating an OAuth inbound integration for each MCP client.

## Before you begin

Role required: oauth_admin, mi_admin, admin

## About this task

For each client that you want to access servers on an instance, create an OAuth inbound integration in Machine Identity Console. To create the OAuth integration, you need a redirect URL from the client. For more information,
refer to the documentation for your AI application and client.

## Procedure

1. Navigate to AllMCP Server Console.
2. From the Configuration tab, select Servers.
3. From the OAuth setup required banner, select Set up OAuth.  
   Alternatively, you can navigate to AllMachine Identity Console and select the Inbound integrations tab.  
   Note:  
   In the list of existing inbound integrations, you might see integrations created with the same names as servers (including underscores). These are integrations for monitoring servers from AI Control Tower and shouldn't be used to integrate with clients.
4. Select New integration.
5. Select OAuth - Authorization code grant.
6. On the form, fill in the required fields.  
   For more information about this form, see [Configure an OAuth authorization code grant](https://www.servicenow.com/docs/access?context=configure-an-oauth-authorization-code-grant&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#create-oauth-inbound-integration-mcp-client__table_acq_zq2_hhc__entry__2}

   | Field | Value |
   |-|-|
   | Details section ||
   | Name | Enter a name for the OAuth integration. |
   | Redirect URLs | Enter the redirect URL for a client. The authorization code is sent to this URL after authentication. To get the redirect URL, refer to the documentation for your AI application and client. To connect to the ServiceNow MCP client on another instance, use the following redirect URL: https://\<client-instance\>.service-now.com/oauth_redirect.do. For more information, see the [Model Context Protocol Client Legacy](https://www.servicenow.com/docs/2HbM4pJ_exqse~VI4QNe~Q "The ServiceNow Model Context Protocol Client (MCP Client) enables you to access the Model Context Protocol tools that are hosted externally and published using an MCP Server in the ServiceNow AI Agent Studio.") documentation. |
   | Auth scope section ||
   | Allow access only to APIs in selected scope | Clear the check box to make the OAuth integration broadly scoped. Important: You must leave this option cleared. If you select this option, clients are unable to fetch tools from the server. |
   | Advanced options section ||
   | Token Format | Select JWT. |
   [Table 1. Inbound integration form]

   {#create-oauth-inbound-integration-mcp-client__table_acq_zq2_hhc}
7. Select Save.  
   Note:  
   If you're prompted to assign an auth scope, select Skip for now.  
   The OAuth inbound integration is created as broadly scoped with a client ID and client secret that you use when configuring the client to connect to servers on the instance.

## What to do next

Configure the client to use the client ID and client secret to authenticate with servers on the instance. For more information, see [Configure an MCP client to connect to an MCP server](https://www.servicenow.com/docs/pBkcH1NbUdpsycrndmkLog "Configure a Model Context Protocol (MCP) client to connect to an MCP server and prompt the server to perform a task.").
* **[Create client authorizations](https://www.servicenow.com/docs/MrxqRUJV_9jeCcOhlz~7~g)**   
  Establish connections between your MCP clients and servers with client authorizations.

*[\>]: and then