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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# ServiceNow(Glide) configuration for IDP

# ServiceNow(Glide) configuration for IDP {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
This process involves setting up the necessary tables and mappings within your ServiceNow instance. This includes configuring ServiceNow, creating the MCP server, and connecting the MCP client.

## Before you begin

Role required: admin  
Important:  
The minimum version required is Australia patch 3 or Zurich patch 10. Microsoft Entra is supported in Australia patch 4 or Zurich patch 11 onwards.

## Procedure

Configure the OIDC provider  
Note:  
Okta is used as the use case to guide you through the steps.

<br />

1. Navigate to the oidc_provider_configuration table and select New.
2. Enter a Name for the OIDC provider.  
   For example, <kbd class="ph userinput">Okta MCP Third Party</kbd>.
3. Set the Cache Configuration Lifespan.  
   The maximum value is 720 hours.
4. Enter the IDP metadata URL into the Metadata URL field.
5. In the User Field, select email.  
   This maps the user claim from the IDP token to the `email` field in the `sys_user` table.
6. Let Enable JT1 claim verification option remain unchecked.  
   Enabling the JSON Web Token Identifier (JTI) would require the MCP client to reauthenticate with every request. Therefore, disabling the JTI check in the OIDC provider configuration is recommended for MCP third-party integrations. This is because the client reuses the same token for tool calls until it expires.
7. Select Submit.

Create the MCP server

8. Navigate to the MCP server console and select Create Server.
9. Enter a name for the server and add the required tools.  
   For example, <kbd class="ph userinput">MCP with Third Party IDP</kbd>.  
   After you create the server, automatically generates an entry in the oauth_protected_resource table and populates it with the list of APIs allowed for that server.

Map the protected resource to the IDP:  

10. Navigate to the oauth_protected_resource_idp_mapping table and select New.
11. In the Protected Resource field, select the resource that was created for your MCP server.  
    If your MCP server name is <kbd class="ph userinput">sn_mcp_server_default</kbd>, the protected resource path is `/sncapps/mcp-server/mcp/sn_mcp_server_default`.
12. In the OIDC Provider field, select the OIDC provider configuration you created earlier.
    1. For Microsoft Entra integrations only, configure the Accepted Audiences field in the `oauth_protected_resource_idp_mapping` table with the Entra Application ID URI (for example, api://\<Application-ID\>.  
       This allows ServiceNow to accept Entra-issued access tokens whose audience claim matches the configured Application ID URI.
    {#servicenow-configuration-for-idp__substeps_xkc_x21_jkc}
13. Select Submit.

## Result

Your MCP server is now configured to authenticate users through the third-party IDP. Users who connect an MCP client to this server are redirected to the related IDP to authenticate.

## What to do next

1. Configure and set up the third-party IDP. This process involves setting up the application and authorization server within the third-party IDP setup. This document uses Okta as the use case, however, Microsoft Entra is also recommended.
2. Integrate and test from your MCP Client.
{#servicenow-configuration-for-idp__ol_emn_vs3_qjc}