Claude + ServiceNow: What the Integration Can (and Can't) Do in 2026
Yes — there’s a ServiceNow-published remote connector in Claude’s directory. No — you almost certainly can’t just flip it on. The connector points at your company’s instance MCP Server, part of ServiceNow’s Action Fabric — there’s no public “mcp.servicenow.com.” Three gates stand between you and a working connection: your instance must be on Zurich Patch 9+ (or Australia Patch 2+), your company needs a Now Assist or AI Native SKU, and an admin must enable and approve the MCP Server in AI Control Tower with OAuth. Behind it sits a real partnership — ServiceNow and Anthropic announced one on January 28, 2026, and Anthropic was the first design partner for Action Fabric at Knowledge 2026. But for an individual user, the honest summary is: enterprise-gated, admin-mediated, and — like every Claude integration — it only works inside a conversation you start.
Here’s exactly what the integration does, what it takes to enable, where the limits bite, and what to use if you want ServiceNow work that runs on its own.
What the connector actually is
ServiceNow’s Action Fabric, launched at Knowledge 2026 (May 5–7), exposes the Now Platform to outside AI agents: an MCP Server Console (inbound — Claude, Copilot Studio, Bedrock and others calling ServiceNow tools), an MCP Client (outbound), and A2A. The MCP Server Console GA’d in December 2025 for Now Assist Skills, with Knowledge Graph and Subflow/Action tools GA in May 2026, included in every Now Assist and AI Native SKU.
Through the directory connector, a permitted user’s Claude can run the tools their admin has exposed — the flagship demo being the same governed playbook that powers a password reset in the ServiceNow UI, running directly from Claude. Every call goes through your instance’s OAuth, ACLs, and audit trail.
What it is not: a way for any Claude subscriber to browse into ServiceNow. If your company doesn’t have the SKU, the patch level, and an admin who has enabled MCP in AI Control Tower, the connector has nothing to connect to. Community MCP servers exist for the gap — osomai/servicenow-mcp does Table CRUD, catalog, and scripts over Basic/OAuth — but they’re unofficial; vet them before handing over instance credentials.
Worth knowing on the partnership: it mostly runs the other direction — Claude is the default model for ServiceNow’s Build Agent, and Claude plus Claude Code went out to ServiceNow’s own 29,000+ employees. That’s ServiceNow using Claude, not your Claude reaching your tickets.
How to set it up (in practice)
- Confirm eligibility: instance on Zurich Patch 9+ or Australia Patch 2+, and a Now Assist or AI Native SKU on the contract.
- Admin work in ServiceNow: enable the MCP Server in AI Control Tower, configure OAuth 2.0/2.1, and choose which skills/tools (Now Assist Skills, subflows, actions) to expose.
- In Claude: add the ServiceNow connector from the directory, point it at your instance, and sign in with your corporate identity. Remote connectors need a paid Claude plan.
- Ask Claude to summarize an incident, look up a change, or run an exposed playbook — all under your instance’s ACLs.
The limits that actually matter
- SKU- and admin-gated. No Now Assist SKU, no MCP Server. This is a procurement-and-platform-team conversation, not a settings toggle.
- Only exposed tools. Claude can use exactly what the admin published to the MCP Server Console — not the whole platform.
- No triggers, no monitoring. Claude acts inside a conversation you start. A P1 incident at 2am doesn’t wake it; a change request stuck in approval doesn’t nudge it. ServiceNow has no native registerable webhooks either — real-time push requires an admin-built Business Rule with outbound REST.
- Laptop-bound for anything scheduled. The nearest thing to autonomy is Claude Cowork’s scheduled tasks, which run on a fixed clock, not on inbox events.
So Claude is great for “work this ticket with me right now” — and not built for “watch the queue and brief me when something breaks.”
If you want ServiceNow work that runs on its own: Carly
The moment you want ServiceNow to reach you — the P1 brief in Slack minutes after it’s filed, the Friday change-window digest, the catalog request filed from a forwarded email — you’ve crossed past what a chat connector does.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. ServiceNow connects to Carly via your own API credentials — an OAuth client or integration-user credentials for the Table API (ask your admin to register one in the Application Registry; its roles gate exactly what Carly sees) — paste them on carlyassistant.com/integrations and it works like any native connection:
- P1 incident watchdog — Carly polls the incident table on an encoded query (
priority=1^active=true^sys_created_on>...) every few minutes; on a new P1 it writes a two-line exec brief from the description and work notes, pings you and the on-call in Slack, and PATCHes a work note that leadership was briefed. - Weekly change-window digest — each Friday, Carly pulls next week’s scheduled change requests plus Aggregate API counts by risk and assignment group, and emails the “what could break next week” summary.
- File a catalog request from an email — forward “need a laptop for the new hire Monday”; Carly extracts the details, orders through the Service Catalog API, replies with the RITM number, and polls until it’s fulfilled.
- Morning approvals brief — pending approvals plus open requests where you’re the requester, compiled into one prioritized email with deep links, before your first meeting.
- No-code setup — describe the workflow in plain English; Carly interviews you and builds it. (Since ServiceNow has no native webhooks, Carly polls on smart filters — and if your admin later adds a Business Rule webhook, events push in real time instead.)
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (ServiceNow connector) | Carly | |
|---|---|---|
| Read / summarize tickets | Yes (tools your admin exposed) | Yes, via Table API |
| Run governed playbooks | Yes (Action Fabric skills) | Via API calls your roles allow |
| Requires Now Assist SKU + Zurich Patch 9+ | Yes | No — Table API works on standard instances |
| Watches queues / reacts to new P1s | No | Yes (polling or webhook) |
| Scheduled digests & briefs | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Emails and Slacks stakeholders | No (Gmail draft-only) | Yes (Gmail + Outlook, Slack) |
| Pricing | Pro $20 / Max $100–$200 + Now Assist SKU | AI agents from $35/mo |
Claude’s connector is a governed hand into ServiceNow for enterprises that have bought in. Carly is a teammate that watches the queue and briefs you on any instance.
Frequently Asked Questions
Does Claude work with ServiceNow?
Yes, with big caveats. A ServiceNow-published remote connector is in Claude’s directory, but it targets your company’s instance MCP Server (Action Fabric) — which requires Zurich Patch 9+ or Australia Patch 2+, a Now Assist or AI Native SKU, and an admin enabling it in AI Control Tower with OAuth. There’s no public ServiceNow endpoint a personal Claude account can use.
What did the ServiceNow–Anthropic partnership announce?
On January 28, 2026: Claude became the default model for ServiceNow Build Agent, the companies are building agentic healthcare and life-sciences apps, and ServiceNow rolled Claude and Claude Code out to its 29,000+ employees. At Knowledge 2026, Anthropic was the first design partner for Action Fabric, connecting Claude to ServiceNow’s “governed system of action.”
Can Claude alert me when a P1 incident is filed?
No. The connector works inside a chat you start, and ServiceNow has no native registerable webhooks for external tools — real-time push needs an admin-built Business Rule with outbound REST. For a watchdog, use a trigger-based agent like Carly, which polls the Table API on encoded queries and briefs you the moment a P1 lands.
How do I connect ServiceNow to Carly without the Now Assist SKU?
Through the standard REST APIs, which every instance has: ask your admin for an OAuth client (Application Registry) or integration-user credentials scoped to the tables you need, then paste them on carlyassistant.com/integrations. Carly uses the Table, Aggregate, and Service Catalog APIs under those roles — no AI SKU required.
More: Claude + Jira · Claude + Slack · Claude + Teams · Claude + Datadog · Claude connectors · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
