Yes: Snowflake Cortex Agents can connect to a remote MCP server, and ServiceNow documents exposing Knowledge Graph functionality as an MCP tool. The deployment is a composition of those documented capabilities—not a jointly validated or vendor-certified Snowflake–ServiceNow runbook. Treat the ServiceNow endpoint, tenant entitlement, OAuth setup, and access policies as items to verify in your own instance before building the connection.
What this integration connects
ServiceNow’s Australia-release documentation, updated July 8, 2026, describes exposing Knowledge Graph functionality to MCP clients through the MCP Server Console. An agent can then use the exposed tool to receive context based on live ServiceNow instance data. The documentation points administrators to a separate procedure for creating a tool from Knowledge Graph; the integration overview alone does not establish the endpoint, licensing, or OAuth details for a particular tenant.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Snowflake Cortex for Beginners: The Practical Guide to AI Functions, Cortex Search, Analyst, and... | $23.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Snowflake documents a separate capability: a Cortex Agent can use an external MCP server. Snowflake’s connector flow uses an API integration for the remote server URL and OAuth configuration, an external MCP server object that references that integration, and an agent specification that includes the external server. Users authenticate with the external service through OAuth.
Together, these capabilities make the integration plausible, but do not establish that every ServiceNow release or instance is compatible with every Snowflake setup. Confirm the exact MCP tool, endpoint, authentication method, and authorization requirements with the administrators of both platforms.
#1 Best Overall
Choose where the client-facing orchestration belongs
The main architecture choice is which system the end user or application calls. The options below describe distinct roles, not mutually exclusive product alternatives.
| Pattern | Client-facing orchestration | Where the tools are hosted | Identity and access to check |
|---|---|---|---|
| Cortex Agent calls ServiceNow MCP | Snowflake Cortex Agent | Knowledge Graph tool exposed by the ServiceNow MCP Server Console | Snowflake role privileges and OAuth integration, plus ServiceNow authentication and instance-side access controls |
| External client calls ServiceNow MCP directly | The external MCP client | ServiceNow MCP server | Client’s ServiceNow authentication and the instance’s tool and data policies |
| External client calls a Snowflake-managed MCP server | The external MCP client; the server exposes Snowflake capabilities | Snowflake-managed MCP tools. Snowflake separately recommends exposing a Cortex Agent as the only client-facing tool when the goal is governed business questions. | Snowflake-managed server and underlying Snowflake authorization. This is distinct from the remote ServiceNow MCP server that a Cortex Agent may call. |
Use the first pattern when the Cortex Agent should be the application’s orchestrator and ServiceNow Knowledge Graph should provide context through a remote tool. A Snowflake-managed MCP server is not a substitute for the ServiceNow remote server in that flow; it serves a different direction of access.
Confirm ServiceNow can expose the intended Knowledge Graph tool
- Verify the feature in the target instance. ServiceNow’s Australia-release “Configuring Knowledge Graph” page, updated March 12, 2026, describes Knowledge Graph as an AI Platform feature available with activation of a ServiceNow generative AI application. It says activation installs the Graph QL plugin and Knowledge Graph application by default, and that Knowledge Graph must be configured for Virtual Agent as part of adoption. These statements provide configuration context; they do not prove entitlement to a particular MCP Server Console feature in your instance.
- Create and expose the tool. Follow the applicable ServiceNow procedure for creating a tool from Knowledge Graph in the MCP Server Console, then confirm that the tool is exposed to the intended MCP client. The July 8, 2026 Australia-release integration page describes the capability but directs administrators to the separate tool-creation procedure.
- Obtain the instance-specific connection details. Have the ServiceNow administrator confirm the exact remote MCP endpoint, supported authentication method, OAuth client registration, authorization scope, and any user authorization requirements. The available platform documentation does not establish universal values for these details.
Set up the Snowflake remote MCP connection
Snowflake’s “MCP Connectors” documentation describes the following sequence. Exact SQL syntax and OAuth values depend on the chosen configuration and are not established here, so use Snowflake’s current instructions and the approved ServiceNow values rather than copying an example for another provider.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Prepare provider details. Obtain the ServiceNow MCP server URL and OAuth details from the instance administrator. Confirm these details are for the intended tenant and tool.
- Create the API integration. Configure the Snowflake API integration with the approved remote server URL, OAuth client credentials, and relevant endpoints. Keep credentials under the organization’s normal secret-management and rotation practices.
- Create the external MCP server object. Configure Snowflake’s external MCP server object to reference the API integration. Confirm both objects are enabled.
- Add the server to the agent specification. Have the Cortex Agent developer include the external MCP server in the agent specification so the agent can discover and call its tools.
- Authenticate users with the external service. Users authenticate through OAuth as required by the configured integration and ServiceNow authorization flow. Do not assume that the Snowflake object setup alone grants a user access to ServiceNow data.
Snowflake describes MCP tool discovery through tools/list and tool invocation through tools/call. Before a tool call, Snowflake checks that the external MCP server and its backing API integration are enabled.
Separate Snowflake privileges from ServiceNow authorization
The Snowflake connecting role needs USAGE on both the external MCP server and its backing API integration to connect and discover tools. Grant those privileges only to roles that need them, and ensure the objects are enabled.
Those Snowflake privileges are not a replacement for ServiceNow-side controls. Separately verify that ServiceNow authentication, tool exposure, and instance policies limit the agent to the intended tools and underlying data. Test using representative identities with only the access they need.
Snowflake warns that external MCP servers are not provided, maintained, or verified by Snowflake. The organization must assess the external server’s trustworthiness, data-processing rights, and applicable third-party terms. In this architecture, Snowflake governs its connector and object privileges; ServiceNow and the organization’s own policies govern the remote service and access to its instance data.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate the integration before rollout
- Confirm the target ServiceNow instance has the required Knowledge Graph capability and that the MCP tool is available in the MCP Server Console.
- Confirm the tool is exposed to the intended client and that administrators have supplied the exact endpoint and authentication configuration.
- Verify OAuth client registration, authorization scope, and user authorization requirements with the ServiceNow administrator.
- Check that the Snowflake API integration and external MCP server object contain the approved configuration and are enabled.
- Check that the Cortex Agent specification references the correct external MCP server.
- Verify the connecting Snowflake roles have only the necessary
USAGEprivileges, and confirm that ServiceNow policies restrict tool and data access as intended. - Observe tool discovery and invocation with representative least-privilege identities before allowing broader use.
If discovery or invocation fails, inspect the corresponding boundary rather than assuming a single shared permission controls the whole path: Snowflake object state and role privileges, OAuth configuration and user authentication, the agent’s server reference, and ServiceNow tool exposure and access policies. Snowflake’s documented discovery and invocation operations provide a useful distinction when determining whether the issue occurs before tool selection or during a call.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
