> Source: https://builder.ema.ai/v2/integrations-data/mcp-servicenow
> Title: ServiceNow MCP Server

# ServiceNow MCP Server

ServiceNow's official MCP server (the **Model Context Protocol Server** application, managed in **MCP Server Console**) runs on each customer's own instance. Every instance hosts its own server at its own URL, so you set the server up on your instance and add it to Ema as an [MCP server](/builder/v2/integrations-data/mcp). Once it's connected, your AI Employees can call the tools you expose from ServiceNow, such as looking up or summarizing incidents.

This page is for the ServiceNow admin and the Ema builder who set this up together. The two of you pass values back and forth: the ServiceNow admin sends the server URL to the Ema builder, the Ema builder sends Ema's redirect URI back, and the ServiceNow admin then sends the OAuth client's credentials.

1.  **ServiceNow admin:** create the MCP server in ServiceNow.
2.  **Ema builder:** add the server in Ema and copy Ema's redirect URI.
3.  **ServiceNow admin:** register an OAuth client for Ema in ServiceNow.
4.  **Ema builder:** add a connection in Ema and sign in to ServiceNow.
5.  **Ema builder:** use the server's tools in an AI Employee.

## Before you begin

In ServiceNow, you need:

-   An entitlement that includes MCP Server Console. It comes with Now Assist, so confirm with your ServiceNow account team that your instance has it. The MCP server is often not enabled on Personal Developer Instances (PDIs) and sandbox instances.
-   The `admin` role to install the application and create the server (`sn_mcp_server.admin` can also create servers). Registering the OAuth client needs `admin`, `oauth_admin`, or `mi_admin`.

In Ema, you need builder access in a workspace that isn't a trial workspace. Trial workspaces can't add MCP servers.

## How authentication works

ServiceNow's MCP server accepts **OAuth 2.0 with the authorization code grant**. In Ema, this is the **OAuth 2.1 (Authorization Code)** option. ServiceNow doesn't support dynamic client registration, API keys, or the client credentials grant, so you register Ema as an OAuth client in ServiceNow yourself, then give Ema that client's **Client ID** and **Client secret**.

Every tool call runs as the ServiceNow user who signed in, with that user's roles and access controls. The connection type you pick in Ema decides whose account that is:

Connection type

Who signs in to ServiceNow

Use it when

**Shared connection**

One account, used by everyone in the workspace

The AI Employee should act as one dedicated ServiceNow user, for example an integration user that has only the roles it needs.

**User connection**

Each person signs in with their own ServiceNow account

Tool calls should follow each person's own ServiceNow permissions, so an employee only sees the records they can already see in ServiceNow.

## Step 1: Create the MCP server in ServiceNow

1.  Install the **Model Context Protocol Server** application (`sn_mcp_server`). Go to **All > System Applications > All Available Applications > All**, search for it, and select **Install**.
2.  Confirm the MCP server is running. Open this URL in a browser, or request it from a terminal. It returns `{"status":"healthy"}`:
    
    ```bash
    curl https://<instance>.service-now.com/sncapps/mcp-server/health
    ```
    
3.  Go to **All > MCP Server Console**, and open **Servers** on the **Configuration** tab.
4.  Pick a server:
    -   **Quickstart Server**: a preconfigured server, named `sn_mcp_server_default`, with tools that look up and summarize incident and case records. Which tools it includes depends on the apps installed on your instance.
    -   **Your own server**: create the tools you need, then create a server, give it a label and a short description, and add your tools to it. A server needs at least one tool. The exact button names differ between ServiceNow releases.
5.  Make sure the server is active. If it shows an **Activate** option, select it. If it shows **Deactivate**, it's already active.
6.  Copy the server URL and send it to the Ema builder. It has this form:
    
    ```text
    https://<instance>.service-now.com/sncapps/mcp-server/mcp/<server-name>
    ```
    

Depending on your ServiceNow release, you can build tools from Now Assist skills, Scripted REST APIs, Knowledge Graph, and synchronous Flow Designer subflows and actions. For a full walkthrough of building tools from a Scripted REST API, see ServiceNow's guide [Building an MCP Server on ServiceNow](https://www.servicenow.com/community/developer-advocate-blog/building-an-mcp-server-on-servicenow-and-connecting-claude-to-it/ba-p/3588171).

> [TIP]
> Tool labels and descriptions you write in MCP Server Console are model-facing: the AI Employee reads them to decide when to call each tool and how to fill its inputs. Start each description with what the tool does, then say when to call it.

## Step 2: Add the server in Ema

> [WARNING]
> You can't change a server's authentication type after you add it. Choose **OAuth 2.1 (Authorization Code)**. If you pick the wrong type, delete the server and add it again.

1.  In Ema, go to **Integrations** and open the **MCP Servers** tab.
2.  Select **Add server**. If the workspace has no MCP servers yet, select **Add MCP server**.
3.  Fill in the form:
    -   **Name**: a display name, for example `ServiceNow`.
    -   **Description**: what the server's tools do.
    -   **Endpoint URL**: the server URL from Step 1.
    -   **Authentication**: **OAuth 2.1 (Authorization Code)**.
4.  Under **Copy this redirect URI to your OAuth provider**, select the copy icon next to the URI. Send the URI to the ServiceNow admin for Step 3.
5.  Select **Add server**.

Ema checks that the endpoint responds like an MCP server before it saves the server. The server has no tools yet: Ema discovers them after you connect in Step 4.

## Step 3: Register an OAuth client for Ema in ServiceNow

1.  In **MCP Server Console**, open **Servers** on the **Configuration** tab. In the **OAuth setup required** banner, select **Set up OAuth**. This opens **Inbound integrations** in Machine Identity Console. You can also go there directly: **All > Machine Identity Console > Inbound integrations**.
2.  Select **New integration**.
3.  Under **Select your application connection type**, choose **OAuth - Authorization code grant**.
4.  Fill in the form:
    -   **Name**: for example `Ema MCP connector`. Don't reuse an integration named after one of your MCP servers: ServiceNow creates those for AI Control Tower, not for clients.
    -   **Redirect URLs**: the redirect URI from Step 2. It must match exactly, with no trailing slash.
    -   Leave **Allow access only to APIs in selected scope** cleared. A narrowly scoped integration can't list the server's tools.
    -   Under **Advanced options**, set **Token Format** to **JWT**.
5.  Select **Save**. If ServiceNow asks you to assign an auth scope, select **Skip for now**.
6.  Copy the **Client ID** and **Client Secret**, and send them securely to the Ema builder. ServiceNow generates both when you save.

> [WARNING]
> Set **Token Format** to **JWT**. With the default opaque format, the connection can succeed but the server returns no tools.

## Step 4: Add a connection in Ema and sign in

1.  In Ema, open your ServiceNow server from the **MCP Servers** tab, and go to its **Connections** tab.
2.  Select **Add connection**, then choose **Shared connection** or **User connection** (see [How authentication works](#how-authentication-works)). You can't change this later.
3.  Fill in the form:
    -   **Connection name**: for example `ServiceNow shared`. **Connection type** shows the choice you made in the previous step.
    -   Ema shows that this server doesn't support automatic registration and asks for a pre-registered Client ID. That's expected. If Ema instead offers **Register automatically** and **Use your own pre-registered app**, choose **Use your own pre-registered app**.
    -   **Copy this redirect URI to your OAuth provider**: the same URI from Step 2. It must match the **Redirect URLs** value in ServiceNow.
    -   **Client ID** and **Client secret**: the values from Step 3.
    -   **Scopes**: `mcp_server`.
    -   **Authorization URL** and **Token URL**: Ema normally finds these and shows them read-only, with an **Override** option. If Ema says it couldn't automatically find them, enter `https://<instance>.service-now.com/oauth_auth.do` and `https://<instance>.service-now.com/oauth_token.do`.
    -   Leave **Token endpoint auth method** on **Automatic (recommended)**.
4.  Select **Save & connect**, sign in to ServiceNow, and select **Allow** on the consent screen.
    -   **Shared connection**: sign in as the ServiceNow user this connection should act as, for example your integration user. That user must be able to sign in interactively to approve the consent screen, so a user set to web service access only won't work. Don't sign in with your own admin account, because everyone in the workspace would then act with your admin access.
    -   **User connection**: sign in with your own ServiceNow account. Other people connect their own accounts later: each person opens the server in Ema, selects the connection on the **Connections** tab, and under **Your connection** selects **Connect**. Opening the server requires builder access.
5.  Ema then discovers the tools your ServiceNow server exposes. To check them, open the **Configure** tab, pick the connection in the **Tools** section, and look at the list. If it's empty, select **Refresh**. **Refresh** is available to Workspace admins and to the server's admins: the person who added it and anyone made an admin on its **Permissions** tab.

Ema refreshes access tokens automatically, so you only need to sign in again if ServiceNow revokes access or the refresh token expires. By default, ServiceNow refresh tokens last 100 days. For more on connections, tool lists, and refreshing, see [MCP Servers](/builder/v2/integrations-data/mcp).

## Step 5: Use the tools in an AI Employee

Autopilot and Orchestrator AI Employees can use MCP servers. Autopilot can use every MCP server in your Workspace, including this one, as long as it has a connection you can use.

To give the server to an Orchestrator AI Employee:

1.  Open the Orchestrator AI Employee and go to **Configuration**.
2.  In the **MCP servers** card, choose **Choose servers**, then select **Add server**.
3.  Pick your ServiceNow server, pick the connection it uses, and select **Add server**.
4.  Save and publish the AI Employee.

A server appears in the list only once it has at least one connection. For the other options, see [Give MCP servers to an AI Employee](/builder/v2/integrations-data/mcp#give-mcp-servers-to-an-ai-employee).

## Troubleshooting

Problem

What to check

Ema can't add the server and reports that the URL doesn't appear to serve MCP

Copy the server URL exactly as MCP Server Console shows it, confirm the server is active, and run the health check from Step 1. If the URL redirects to the ServiceNow sign-in page instead of answering, the MCP server isn't enabled on the instance: contact ServiceNow support.

Sign-in to ServiceNow fails or reports a redirect error

The **Redirect URLs** value on the ServiceNow inbound integration must exactly match the redirect URI Ema shows, with no trailing slash.

Ema asks for the **Authorization URL** and **Token URL**

Ema couldn't find ServiceNow's sign-in endpoints on its own. Enter `https://<instance>.service-now.com/oauth_auth.do` and `https://<instance>.service-now.com/oauth_token.do`.

ServiceNow rejects the requested scope

Check the **Scopes** value on the connection. Some instances expect `useraccount` instead of `mcp_server`.

The connection succeeds but no tools appear

Check that **Token Format** is **JWT** on the inbound integration, that **Allow access only to APIs in selected scope** is cleared, and that the server has at least one tool and is active. Then connect again, select the connection in the **Tools** section of the **Configure** tab, and select **Refresh**.

Tool calls fail with permission errors

The signed-in ServiceNow user needs the roles for the records the tool touches, for example `itil` for incidents. Tools built from flows or actions also need an access control that allows the `invoke_from_ai` operation.

Sign-in goes to your identity provider first

This is expected when your ServiceNow instance uses single sign-on.

## What's next

-   [Data Connectors](/builder/v2/integrations-data/data-connectors): sync external documents into Knowledge bases so an AI Employee can cite them.
-   [MCP Servers](/builder/v2/integrations-data/mcp): manage connections, refresh tool lists, and fix discovery errors for any MCP server, including this one.
-   [ServiceNow-Backed Queues](/builder/v2/ticketing/servicenow-queues): if you want Ema's ticket queues to read and write ServiceNow incidents directly, use a ticketing connection instead of an MCP server.
