Sign in Book a demo
Back to Tools
Customer Support OAuth
Build Your Agent View ServiceNow Docs
servicenow logo

ServiceNow MCP Tools for AI Agents

Let an agent search incidents, read knowledge articles, create and update records, and order items from the ServiceNow catalog.

Available Tools

17 tools available in this integration

Servicenow.AddComment

Add a comment or internal work note to a work record.

Servicenow.CreateIncident

Open a new incident.

Servicenow.GetCatalogItem

Read a catalog item's details and the options required to order it.

Servicenow.GetConfigurationItem

Read a configuration item together with what it depends on and what depends on it.

Servicenow.GetKnowledgeArticle

Read a knowledge article's full body.

Servicenow.GetRecord

Read a work record together with its full comment and work-note history.

Servicenow.GetRecordCounts

Count work records matching a filter, optionally broken down by a field.

Servicenow.GetRecordFieldChoices

Discover the valid choice values for a work-record field on this instance.

Servicenow.OrderCatalogItem

Order an item from the service catalog.

Servicenow.SearchAssignmentGroups

Find ServiceNow assignment groups by full or partial name, to route work to them.

Servicenow.SearchCatalogItems

Find service catalog items matching a described need.

Servicenow.SearchConfigurationItems

Find configuration items (systems) by name, optionally narrowed to a CMDB class.

Servicenow.SearchKnowledgeArticles

Search the knowledge base for articles matching a described problem or topic.

Servicenow.SearchRecords

Find work records of one type by text, assignment, state, priority, or recency.

Servicenow.SearchUsers

Find ServiceNow users by name or email, to assign or contact them.

Servicenow.UpdateRecord

Change one or more fields on a work record.

Servicenow.WhoAmI

Return the authenticated ServiceNow user's profile.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the open incidents about VPN access, summarize the latest work notes, and route the right ones." Arcade picks the right ServiceNow actions without guessing record types, assignment groups, or user IDs.

Up to 100x fewer tokens

ServiceNow searches and record reads return focused fields, counts, choices, and matching records instead of an entire instance, so the agent can investigate incidents without loading unrelated history or CMDB data.

Complete the workflow end to end

Search an incident, read its history, check the knowledge base, inspect dependencies, update the record, and add a work note through one toolkit designed around the complete ITSM task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing ServiceNow

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For ServiceNow, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Servicenow.OrderCatalogItem from agents unless the roles your IDP marks as approved requesters are active, so an agent cannot order equipment or paid services for your organization.
  • Restrict Servicenow.UpdateRecord to agents operating under your incident-manager or change-manager roles, so routine automation cannot alter ownership, priority, state, or approval fields.
  • Show Servicenow.CreateIncident only to agents serving your support or operations roles, so untrusted workflows cannot flood your incident queue with fabricated tickets.
Pre-execution before each tool call
  • Require human approval before Servicenow.OrderCatalogItem runs, so an agent cannot place a service request or purchase without a person confirming the details.
  • Block Servicenow.CreateIncident when the description contains credentials, access tokens, or customer secrets, so sensitive data is not copied into incident records.
  • Refuse Servicenow.AddComment when the comment contains passwords, tokens, or payment details, so an agent cannot publish secrets in a work record's history.
Post-execution after the tool returns
  • Redact Servicenow.GetRecord results to remove phone numbers, personal email addresses, credentials, and full comment or work-note bodies before they reach the model.
  • Strip personal email addresses, phone numbers, and other private contact fields from Servicenow.SearchUsers results, leaving only the identity details needed for assignment.
  • Deny Servicenow.GetKnowledgeArticle output when the article is marked confidential, restricted, or under legal hold, so its contents never reach the model.

How to use ServiceNow with your agent

Pick an MCP client below and follow the setup to connect ServiceNow to your agent. Each user authorizes their own ServiceNow account.

Your questions, answered

A ServiceNow MCP server exposes ServiceNow capabilities as structured tools an AI agent can call through the Model Context Protocol. After a user authorizes their account, the agent can search and read work records, consult knowledge, update incidents, and order catalog items within that user's permissions.

Arcade provides the MCP runtime for ServiceNow rather than a ServiceNow first-party MCP server. Arcade adds per-user OAuth, agent-optimized actions, approval workflows, response redaction, and controls for reaching the same tools from different clients.

Arcade agents can search, count, read, create, comment on, and update work records; find users and assignment groups; search and read knowledge articles; inspect configuration items; search and order catalog items; discover valid field choices; and identify the authenticated user.

Arcade requests the ServiceNow access your enabled actions require. The connected user's ServiceNow roles and ACLs still determine what the agent can read or change, including records, knowledge, CMDB data, users, catalog items, and write operations.

Yes. Each user authorizes their own ServiceNow account through OAuth. Actions run under that user's authorization and ServiceNow permissions, so one user cannot use the agent to access another user's data unless ServiceNow permits it.

Yes. Contextual Access policies can require human approval before consequential ServiceNow actions such as creating or updating an incident, adding a work note, or ordering a catalog item. The call proceeds only after the policy's conditions are satisfied.

Arcade proxies ServiceNow API calls and does not persist your content as part of normal tool execution. Credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's ServiceNow authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, actions stop until the user reconnects their ServiceNow account.

ServiceNow instance and API rate limits still apply to actions performed through Arcade. The available details do not specify a separate Arcade limit or a fixed ServiceNow quota, so high-volume workflows should follow the limits configured by the instance.

Ready to actually ship your agent?

Connect your agent to ServiceNow with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the ServiceNow Quickstart