Use this file to discover all available pages before exploring further.
The ServiceNow app provides read/write access to the ServiceNow ITSM platform via its Table API. It can be used either as a Builder app (automations call ServiceNow instructions directly) or as a remote MCP server consumed by an Knowledges agent — covering incidents, change requests, problems, service catalog, requests, attachments, users and groups.
ITSM Tickets
Incidents, changes and problems with transitions and work notes
Service Catalog
List, inspect and order catalog items with variables
Generic Table Access
Query any ServiceNow table with encoded queries and aggregates
A ServiceNow instance (URL format: https://<instance>.service-now.com)
Either Basic Auth credentials (user with itil / admin role) or an OAuth2 client (client_credentials flow)
Roles required for the intended tables: itil for incidents, change_manager for changes, problem_manager for problems, sn_request_write for catalog requests, etc.
Required when authType = oauth2 (uses client_credentials grant)
MCP Endpoint
Auto-populated on install — URL of the MCP endpoint for this instance
MCP API Key
Auto-populated on install — signed key used in the mcp-api-key header. Do not modify
Credentials are stored as workspace secrets. MCP Endpoint and MCP API Key are generated automatically by the onInstall flow and are only needed to expose this instance as an MCP server (see the next tab).
Every instruction resolves credentials via buildAppAuth (Basic or OAuth2 depending on authType). Most list operations accept limit, offset, fields (comma-separated) and displayValue (true/false/all) to control the response shape.
displayValue controls how reference/choice fields are rendered: true → labels, false → sys_ids, all → both (under value and display_value).
The ServiceNow app ships with a built-in MCP server. Each app instance gets its own signed mcp-api-key that encodes the workspace ID and a credentials lookup URL — ServiceNow credentials (Basic or OAuth2) are never passed through headers and are resolved server-side from the app configuration.
Agents consume MCP servers directly through Agent Creator capabilities. This is the preferred way to expose ServiceNow to an agent.
1
Create or open a workspace
From the Prisme.ai console, create a new workspace (or open the one that will host the connector).
2
Install the ServiceNow app
Open the workspace Imports panel, search for ServiceNow and install it.
3
Configure the credentials
Open the freshly installed app instance settings and fill in the required fields (see the Usage as App tab for the field-by-field reference).
4
Copy the MCP endpoint and API key
Still on the app instance configuration page, copy the values of MCP Endpoint and MCP API Key — both are generated automatically on install.
5
Open Agent Creator
Switch to Agent Creator and open the agent you want to extend.
6
Add a capability
Add a new capability to the agent:
If a dedicated ServiceNow capability exists — select it and paste the MCP API Key into the mcp-api-key field. The server URL is already wired.
Otherwise — select the generic custom_mcp capability, paste the MCP Endpoint into the Server URL field, then open the Headers field and add an mcp-api-key entry whose value is the MCP API Key copied earlier:
{ "mcp-api-key": "your-mcp-api-key"}
7
Save
The agent now has access to every ServiceNow tool exposed by the MCP server.
8
Brief the agent in its system prompt
Wiring the capability is not enough — the agent also needs to know the MCP exists and when to reach for it. Add a short paragraph to the agent’s system prompt. Copy-pasteable starter:
You have access to the ServiceNow MCP server. Use it whenever the user asks about ITSM data — incidents, change requests, problems, tasks, requested items, knowledge articles or service catalog entries. Examples: "List my open incidents", "Create a change request for the database upgrade tonight", "What's the status of INC0012345?", "Find the knowledge article on VPN troubleshooting". Prefer calling MCP tools directly over guessing, and confirm with the user before any destructive action (resolve an incident, close a problem, approve a change).
Refine the trigger keywords (assignment groups, ticket prefixes, knowledge categories) so the agent reliably picks up the right intent in your context.
Use this flow to plug the ServiceNow MCP into an Knowledges agent that does not yet support the native MCP picker.
1
Install the ServiceNow app
Install and configure the app in the same workspace as your agent (see the Usage as App tab). Once configured, mcpEndpoint and mcpApiKey are auto-populated.
2
Copy the MCP credentials
Open the app instance config and copy the values of MCP Endpoint and MCP API Key.
3
Open your Knowledges project
Navigate to Advanced > Tools.
4
Add an MCP tool
Click Add and select the MCP tab.
5
Fill in the endpoint
Paste the MCP Endpoint URL copied from the app instance.
6
Add the auth header
In the Headers field, add the signed API key:
{ "mcp-api-key": "your-mcp-api-key"}
7
Save
The agent can now list and call ServiceNow tools through the MCP endpoint.
The signed mcp-api-key encodes the workspace ID and the getConfig webhook URL. The MCP server validates the signature using the central app secret and transparently fetches the ServiceNow instance URL and credentials (Basic or OAuth2) from the installed app. Credentials are cached per tenant for 10 minutes.
The MCP server uses whatever mode is configured on the app instance:
Basic Auth — authType: basic, sends Authorization: Basic <base64(username:password)> on every call.
OAuth2 Client Credentials — authType: oauth2, the MCP server exchanges clientId / clientSecret for an access token against /oauth_token.do and caches it, then sends Authorization: Bearer <token>.
Switch modes by editing the app instance configuration; no MCP tool lets you change credentials at runtime.
“Instance not configured” — instanceUrl is missing from the app config. Paste the full URL with scheme (https://acme.service-now.com).“Basic Auth requires username and password” — authType is basic but one credential is empty. Either fill both or switch to oauth2.“OAuth2 requires clientId and clientSecret” — authType is oauth2 but the client credentials are missing. Create an Application Registry in ServiceNow (System OAuth > Application Registry) with the client_credentials grant.“Invalid API key” (MCP) — The mcp-api-key header does not match the central app secret. Reinstall the app instance to regenerate a signed key.Empty results with a seemingly valid query — encoded queries are case-sensitive and ACL-filtered. Try displayValue: all and verify the effective roles of the account.