Labsco
MCP SERVER

ServiceNow

by habenani-p

Query, build and automate a ServiceNow instance in plain English - incidents, CMDB, flows, scripting and reporting.

ERP & Vertical Business Systems
Summary
Impact analysis before the change is the part worth having.

A tool surface this large is mostly a question of what you switch on. The distinctive piece is the dependency work - finding what references a field or calls a script before you touch it - which is the question that normally costs an afternoon in the platform UI. Read-only by default is the right posture for an instance other people depend on.

What it is

A broad ServiceNow server covering ITSM, ITOM, CMDB, HRSD, CSM, Flow Designer, scripting and portal - over 450 tools in total. It is read-only unless you turn writing on, so a production instance cannot be changed by accident.

What you get
  • Records read and queried across the standard modules, with server-side aggregate reporting that returns counts and averages rather than truncated rows
  • Impact analysis before a change: what depends on a table, where a field is referenced, and where a script is called
  • Table schemas, reports, scheduled jobs and system logs read directly from the instance
  • Automated test framework work - suites, tests, results and failure insight
  • Local Sync, which pulls instance artifacts down to files you can read and diff
  • Writing, scripting and CMDB changes behind opt-in flags
Requirements

Node.js 20 or higher and npm install -g nowaikit. A ServiceNow instance URL plus credentials - basic username and password in the environment, or OAuth, which the vendor documents separately. The setup wizard detects your AI clients and writes their configuration. No instance of your own? A free personal developer instance works. The licence is source-available, not open source.

Setup effort

One command plus a key — npm install -g nowaikit, then supply credentials