ServiceNow expands OpenAI deal, with integrations still ahead

OpenAI and ServiceNow expanded their partnership on October 28. The ServiceNow MCP plugin is available in the OpenAI marketplace, according to the announcement. Larger integrations remain planned, not simultaneously launched.
What is available and what is still planned
| Capability | Announced timing |
|---|---|
| ServiceNow MCP plugin | Available October 28 |
| Enhanced plugin capabilities | Expected by the end of 2026 |
| Control Tower voice | Expected Q1 2027 |
| OpenAI-powered security capabilities | Early access expected January 2027, GA planned Q2 |
| Codex in AI Workflow Factory | Expected in 2027 |
Customers connect their own ServiceNow instance and select capabilities. OpenAI says Action Fabric applies existing permissions and business rules. Interactive experiences inside ChatGPT are being previewed, not presented as universally available today.
Marketplace presence is not a complete deployment checklist
ServiceNow’s MCP Server Console documentation says access to application features, AI skills, workflows and agents depends on licensing. That is background platform documentation, not a new entitlement granted by the partnership. A marketplace listing alone does not establish what a particular customer can use.
The connection guide describes an OAuth inbound integration and client configuration using server details. It explicitly says the client-side process depends on the AI application. Teams should use the relevant client instructions rather than treating a generic MCP example as verified setup for this plugin.
Check the actual tool catalog
A ServiceNow employee-authored FAQ explains why two installations may expose different capabilities. The Quickstart Server’s tools depend on installed Now Assist apps. ITSM provides incident lookup and summarization. Additional HRSD or CSM apps can add case tools. These are platform examples, not a promise that every tool is included in the new ChatGPT plugin.
The same FAQ distinguishes human users from autonomous integrations. Tool calls use the authenticated person’s identity or the dedicated integration identity configured for the agent. Existing roles and access controls determine what that identity can do. Administrators also decide which tools a server exposes.
The FAQ recommends scoped servers rather than one catalog containing everything. A shared tool definition can appear on several servers, so editing it affects every place it is used. Review those dependencies before changing a description or input configuration.
An incident pilot should prove more than a good answer
An illustrative evaluation could start with a small set of sanitized test incidents. Ask the connected assistant to retrieve one known record and summarize it. Compare the result with the source, including the assignment group, status and missing information. Then separately evaluate an allowed update, checking the resulting record rather than trusting the conversational confirmation.
Use a test identity with limited access and include a record it should not retrieve. Record the expected behavior before testing. This is a proposed evaluation, not a test ByteForward performed or a claim that the integration has passed it. Keep permission checks separate from whether a summary sounds convincing.
The announcement does not provide a complete customer pricing or plan matrix. Confirm licensing, available tools, data handling and expected charges with the relevant account teams before committing. Future roadmap dates are planning targets, not features to count as deployed.
This is distinct from ServiceNow Flow, the standalone service desk covered earlier. Do not transfer that product’s access conditions or published rates to this integration. ByteForward reviewed the sources but has not connected a ServiceNow instance or tested the plugin.
Featured image: AI-generated editorial illustration by ByteForward. Logo references from OpenAI and the ServiceNow newsroom. Marks belong to their respective owners. No affiliation or endorsement is implied.


