ServiceNowAI & Automation

ServiceNow in ChatGPT: A UK Governance Gate for the New MCP Plugin

ServiceNow's MCP plugin for ChatGPT went live in the OpenAI marketplace on 28 October 2026, letting employees run governed ServiceNow workflows through Action Fabric. Here is the gate I would put in front of it before it touches a UK production instance.

AQ
Ali Qaiser
AWS Certified | ServiceNow Architect | Enterprise AI Consultant
30 October 2026
8 min read
ServiceNow in ChatGPT: A UK Governance Gate for the New MCP Plugin
In brief

ServiceNow's MCP plugin for ChatGPT went live in the OpenAI marketplace on 28 October 2026, letting employees run governed ServiceNow workflows through Action Fabric. Here is the gate I would put in front of it before it touches a UK production instance.

Key Takeaways
  • ServiceNow and OpenAI expanded their partnership on 28 October 2026.
  • The ServiceNow MCP plugin is available in the OpenAI marketplace now, with enhanced capabilities expected by end of 2026.
  • OpenAI agents reach ServiceNow workflows through Action Fabric with existing permissions and approvals.
  • Restrict who can enable the plugin until it is registered with an owner.
  • Run it as the signed-in user, never as an elevated integration account.
  • Start with a few low-risk workflows and keep sensitive record changes out of scope.
  • Update the DPIA and privacy notice, and confirm processing and retention in writing.
  • Prove deny paths and rehearse switching the OAuth application off.

What changed

On 28 October 2026 ServiceNow announced an expanded partnership with OpenAI. The parts that matter to anyone running a ServiceNow estate in the UK:

  • A ServiceNow MCP plugin is available in the OpenAI marketplace today, letting people complete governed ServiceNow workflows from inside ChatGPT. ServiceNow says enhanced capabilities are expected by the end of 2026.
  • OpenAI agents will reach ServiceNow workflows through ServiceNow Action Fabric, carrying the enterprise context, permissions and approvals the organisation already requires.
  • Codex is coming to AI Workflow Factory (expected 2027), voice in the Super Intelligence Control Tower is expected in Q1 2027, and OpenAI-powered Security and Risk capabilities are expected in early access in January 2027, with general availability planned for Q2 2027.
  • OpenAI is a founding member of ServiceNow's new Control Tower Alliance.

Most of that is roadmap. The plugin is not. It is live now, and that means someone in your organisation can probably connect ChatGPT to your production instance this afternoon.

Why this is a different front door

For years the ServiceNow front doors were the portal, the agent workspace, Virtual Agent, email and integrations you built and owned. A ChatGPT plugin adds a front door that sits outside your instance and outside your release process. The workflow still runs in ServiceNow, but the conversation, the prompt and the decision to call a tool happen in a third-party product.

ServiceNow's own research, published on 20 October 2026, is a useful reminder of why this matters. It reported that nine in ten organisations had an agentic AI security incident in the last year, that 29% of security teams found agents running in production that had never been registered, and that only 13% had a defensible agentic security programme. A marketplace plugin that anyone can enable is exactly how unregistered agents appear.

The gate I would put in front of it

1. Decide who is allowed to connect it

Before anything else, check whether your ChatGPT workspace lets users add marketplace plugins themselves. If it does, restrict it to admins until the steps below are done. On the ServiceNow side, the plugin should authenticate through an OAuth application you have registered and named, not through a shared integration account.

2. Register it as an agent, not as a browser

Record the plugin in the CMDB and in AI Control Tower (now the Super Intelligence Control Tower) as a business service with a named owner, a support group and a change model. If it is not in the inventory, it is shadow AI with a logo.

3. Act as the user, never as admin

The most important design choice is identity. The plugin should act with the signed-in employee's own roles, so that ACLs, data policies and approvals apply exactly as they do in the portal. Treat any proposal to run it under an elevated integration user as a red flag. If roles are messy, fix them first: an over-privileged employee becomes an over-privileged assistant.

4. Start with a short list of workflows

Do not expose everything on day one. Pick a few low-risk, high-volume journeys, such as checking ticket status, raising a standard request or searching knowledge, and keep record changes on changes, assets and HR cases out of scope until you have evidence.

5. Do the UK GDPR paperwork properly

Conversation content now passes through OpenAI as well as ServiceNow. Update the DPIA and record of processing, confirm in writing where prompts and outputs are processed and retained under your ChatGPT agreement, and update the employee privacy notice. HR, health and case data deserve an explicit "not via ChatGPT" decision until legal has signed off.

6. Prove the deny path

Write tests for what must not happen: a user without the role asking for someone else's HR case, a request to approve their own change, a prompt that tries to bulk-update records. Run them before each scope increase and keep the evidence for audit.

7. Make it observable and stoppable

Tag plugin-originated transactions so you can report on them separately, alert on unusual volume, and rehearse switching the OAuth application off. If you cannot stop it in five minutes, you are not ready for wider rollout.

What I would tell a CAB

The ChatGPT plugin is a sensible way to meet employees where they already work, and Action Fabric is the right place to enforce permissions. But it is a new channel into production, live now, and easy to enable. Treat it as an agent with an owner, scope it tightly, run it as the user, and prove you can refuse and stop it. The 2027 roadmap items can wait for their own gates.

Expert Commentary

The plugin itself is sensible: it meets people where they already work and Action Fabric is the right place to enforce permissions. The risk is how easy it is to switch on. Treat it as an agent with an owner, run it as the user, and prove you can refuse and stop it before you widen scope.

Topics
ServiceNowOpenAIChatGPTMCPAction FabricSuper Intelligence Control TowerAI GovernanceUK GDPRCABUK
All insights

Need Help With Your Implementation?

Arrange a consultation about ServiceNow, AI agent automation or AWS.

Schedule a Consultation