Model Context Protocol connectors

  • Release version: Australia
  • Updated June 5, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Model Context Protocol connectors

    Model Context Protocol (MCP) connectors within ServiceNow Connect Hub enable AI agents to seamlessly access tools and data from external systems via a standardized communication protocol. MCP is an open protocol that facilitates AI agents discovering, invoking tools, retrieving resources, and sharing context with third-party applications without requiring custom integration logic for each system. This enables coordinated, context-aware workflows across models and external systems.

    Show full answer Show less

    Key Features

    • MCP Connectors: Configured connections between ServiceNow and external MCP-compatible servers, allowing AI agents to leverage external system capabilities.
    • MCP Registry: A private ServiceNow registry where AI models, agents, and teams discover approved MCP servers to solve business problems with governance. It supports integrations with AI Agent Studio and others.
    • OAuth 2.1 Client Registration Methods: Supports two methods for connecting MCP connectors to external systems:
      • Dynamic Client Registration: Automates OAuth setup by negotiating client credentials during connection, offering fewer steps and automatic credential rotation managed by the provider.
      • Manual Client Registration: Requires manual creation and configuration of an OAuth application in the third-party system, supplying Client ID and Client Secret to Connect Hub.
    • Certified Connectors: Connectors tested and approved by ServiceNow are labeled "Certified by ServiceNow" in the MCP Registry.
    • Custom Connectors: When a needed connector is not in the registry, customers can define custom MCP connectors by specifying the MCP endpoint URL and authentication details.
    • Authentication Methods for Custom Connectors: Includes OAuth 2.1 (recommended), API key, and Basic Authentication to meet various security requirements.

    Key Outcomes

    • Enables AI agents to integrate with a wide range of third-party applications efficiently and securely without custom coding per integration.
    • Provides enterprise governance and approval for MCP servers, ensuring autonomous AI decisions comply with organizational policies.
    • Simplifies OAuth authentication management via dynamic client registration, reducing operational overhead and improving security.
    • Offers flexibility to connect with systems not yet supported by the registry through custom connector creation.

    Model Context Protocol (MCP) connectors in Connect Hub enable AI agents to access tools and data from external systems using a standardized communication protocol.

    MCP is an open protocol that defines how AI agents communicate with external systems to discover and invoke tools, retrieve resources, and share context. By standardizing this communication layer, MCP allows AI agents to interact with a wide range of third-party applications without requiring custom integration logic for each one.

    In Connect Hub, an MCP connector represents a configured connection between ServiceNow and an external system that exposes an MCP-compatible server. Once an MCP connector is set up, AI agents can use it to access the tools and capabilities that the external system provides, enabling coordinated, context-aware workflows across models and systems.

    MCP Registry

    ServiceNow MCP Registry is a private registry where large language models (LLMs), AI agents, and teams discover and connect to approved MCP servers, finding the best tool for every business problem, governed at every step. The Registry enables AI models and humans query available MCP servers and select the ones best suited to solve a business problem. Every server exposed to an LLM is pre-approved in AICT, helping to ensure autonomous decisions never bypass enterprise governance. It works with AI Agent Studio, Claude, and so on. For more information, see ServiceNow MCP Registry.

    MCP connector registration methods for OAuth 2.1

    Connect Hub supports two OAuth client registration methods for connecting to external systems: manual client registration and dynamic client registration. When the MCP registry does not include a connector for the system you need, you can define a custom connector. Connectors that are tested and approved by ServiceNow display a Certified by ServiceNow label in the registry.

    Dynamic client registration automates the OAuth application setup between Connect Hub and the third-party provider. Instead of requiring you to create an OAuth application manually, the provider and Connect Hub negotiate the client credentials automatically as part of the connection flow. When a connector may probably require manual setup, the registry entry displays the label Manual setup may be required next to the connector name.

    Dynamic client registration offers the following advantages over manual registration:

    • Credentials are managed by the provider and rotated automatically, reducing the risk of credential exposure.
    • The connection workflow is completed in fewer steps.

    Manual client registration requires you to create and configure an OAuth application in the third-party system's developer settings before connecting the MCP connector. During this process, the third-party system issues Client ID and a Client secret, which you provide to Connect Hub to authorize the connection.

    The MCP registry in Connect Hub includes connectors for a curated set of third-party systems. If the registry does not contain a connector for the system you need, you can define a custom connector by providing your own MCP endpoint URL and authentication configuration.

    Authentication methods for custom connectors

    When creating a custom MCP connector, you select an authentication method that matches the security requirements of your external MCP server. The following authentication methods are supported:

    • OAuth 2.1: The recommended method for MCP connectors. Supports both Dynamic Client Registration, where the server auto-populates client details, and Manual Client Registration, where you supply the client credentials directly.
    • API key: Uses a static key issued by the third-party application to authenticate requests to the MCP server.
    • Basic Authentication: Authenticates using a username and password associated with the MCP server.