Integrating MCP server with third-party identity providers
Configure the ServiceNow® Model Context Protocol (MCP) server to authenticate users through a third-party identity provider (IDP).
When you integrate a third-party IDP with an MCP server, users authenticate through the external IDP instead of ServiceNow's native authentication. This process involves three phases:
- ServiceNow (Glide) configuration
- Third-part IDP setup
- Integration and testing
The first phase is ServiceNow (Glide) configuration that involves setting up the necessary tables and mappings within your ServiceNow instance. This has three steps:
- Configure the OIDC provider
- Create the MCP server
- Map the resource to the IDP
The second phase is Third-party IDP setup that involves setting up the application and authorization server within the IDP. This has three steps:
- Account setup
- Create an app integration
- Configure the authorization server
The final phase is Integration and testing that involves connecting the MCP client (such as Claude Desktop) to the configured systems. This involves three steps:
- Connect to the MCP client
- Authenticate
Verify tool calls
ServiceNow(Glide) configuration for IDP
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.- Integrate and test IDP with MCP server
This phase within integration of MCP server with IDP involves connecting the MCP client (such as Claude Desktop) to the configured systems.
Parent Topic:Connecting to an MCP server from an MCP client
Related topics