The Universal MCP Client is the foundational connectivity layer for AI Agents on the Now Platform. It gives every ServiceNow application, on-Glide and off-Glide, a single governed path to invoke tools and access resources from any MCP-enabled server. Access is gated through AI Control Tower at runtime, meaning governance is not a configuration step teams can skip. It is wired into the execution path before any MCP call goes out. Developers can also invoke MCP Servers directly from server-side logic using the MCPClient Script Include, purpose-built for ServiceNow scripting contexts.
The client ships with complete MCP protocol coverage including Connected MCP Server Discovery, Known Tools, Invoke Tool, Known Resources, and Read Resources. Onboard an MCP Server once and it becomes available across every ServiceNow application through a single flow that handles AICT approval requests. Off-Glide consumers connect via REST APIs built on MCP Verbs, making this the first MCP client on the Now Platform purpose-built for off-platform execution. When the MCP specification evolves, one update to the MCP Client covers every consumer automatically, with no changes required by individual teams. For developers building custom integrations, the MCPClient Script Include exposes a clean scripting API with functions for Get Servers, Get Tool List, and Invoke Tool, making it straightforward to call any registered MCP Server directly from business rules, flow actions, or custom script includes.
MCP Client APIs now support product-level identification and telemetry. Users can now specify a product when interacting with MCP Client APIs, enabling tracking and aggregation of usage across products. Telemetry events are emitted for both MCP operations and tool invocations, allowing measurement of adoption and usage. Each operation and tool call generates a corresponding telemetry event, capturing product, method, server, status, and tool name.
ServiceNow
Other Requirements:None