ServiceNow

Every catalog item, incident form, change request, and approval flow instantly callable by Now Assist agents. No JSON schema writing, no RPA scripting. Drop auto-webmcp into a UI Script and it handles everything automatically.

Works today. No platform changes needed. ⏱ ~10 min to deploy Scoped app safe

1 Add a Global UI Script

1
In ServiceNow, open the Application Navigator and search for UI Scripts (System UI › UI Scripts).
2
Click New to create a new UI Script.
3
Set Name to auto_webmcp_loader, set API Name to auto_webmcp_loader, and ensure Global is checked so it runs on all pages.
4
Paste the script below into the Script field, then click Submit.
5
Hard-refresh any ServiceNow page and open the browser console. You should see [auto-webmcp] registered N tools.

// auto-webmcp loader — UI Script (Global)
// Loads auto-webmcp from CDN and activates it on every ServiceNow page.
// Requires the WebMCP flag in the user's browser (chrome://flags/#enable-webmcp-testing)
(function () {
  'use strict';

  // Don't load more than once per page (SN sometimes runs UI Scripts twice)
  if (window.__AUTO_WEBMCP_LOADED) return;
  window.__AUTO_WEBMCP_LOADED = true;

  var script = document.createElement('script');
  script.src = 'https://cdn.jsdelivr.net/npm/auto-webmcp@0.2.1/dist/auto-webmcp.iife.js';
  script.async = true;
  script.onload = function () {
    // auto-webmcp auto-inits on load; nothing else needed.
    // Optional: pass config to customise tool names or enable debug mode.
    // window.autoWebMCP({ debug: true });
  };
  document.head.appendChild(script);
}());

2 Alternative: Service Portal widget script

If you only want auto-webmcp active inside the Service Portal (not the classic UI), inject the script from a portal page's Header script tag instead.

1
Navigate to Service Portal › Portals and open your portal record.
2
Open the portal's Theme, then scroll to the Header widget.
3
In the widget's Client Script, add the same loader snippet from Step 1.
4
Save and reload the portal. Done.

3 Optional: enrich tool names with spec attributes

auto-webmcp infers tool names and descriptions automatically from the DOM. For critical forms where you want precise agent instructions, add these attributes to the <form> element in the ServiceNow widget HTML template.

<form
  toolname="create_incident"
  tooldescription="Create a new IT incident ticket with priority, category, and description."
  toolautosubmit="true"
>
  ...
</form>

ℹ️ Without these attributes auto-webmcp still works. It infers a tool name from the page title and heading. Add them only when the inferred name isn't specific enough.

4 What gets registered automatically

ServiceNow forms that become AI-callable out of the box

Service Catalog items: every catalog form with its variable fields
Incident creation: short description, category, priority, assignment group
Change requests: type, risk, description, justification fields
Access requests & approvals: requester, role, justification
Employee onboarding forms: name, department, equipment requests
Knowledge article submissions: title, category, body

Password, file, and hidden inputs are never exposed to agents. auto-webmcp automatically skips these field types regardless of configuration.

5 Packaging as a scoped app (optional)

For ServiceNow Store distribution: wrap the UI Script in a scoped application. Create a new scoped app in Studio, add the UI Script to it, and submit through the ServiceNow Build Partner program. This allows IT admins to install auto-webmcp from the Store without touching code.

Community resources: join the Now Community and post in the "Developer" and "AI/Automation" forums to find other admins already using auto-webmcp with Now Assist.

Next steps

Test it

Try auto-webmcp in your browser console →

Another platform

HubSpot install guide →