Write, scripting and CMDB changes are opt-in flags, so pointing this at a production instance cannot modify it by accident. The second lever is the tool package: the full set is 450+ tools riding along in every turn, while a help-desk user genuinely works with 23 of them.
A ServiceNow MCP server spanning ITSM, ITOM, CMDB, HRSD, CSM, Flow Designer, scripting and portal — 450+ tools, loadable as role-specific subsets so a client only carries the ones its user needs.
- Incidents, changes, approvals, knowledge, catalog, SLAs and tasks queried and updated in plain English
- Impact analysis before you change anything — `list_table_config`, `find_field_references` and `find_script_references` show what depends on a table, field or script
- `aggregate_report` runs counts and averages server-side, so a report isn't cut off at 1,000 rows and comes back chart-ready
- Local Sync — pull widgets and scripts down to local files, edit them, push them back
- Role packages selected with `MCP_TOOL_PACKAGE`: `service_desk` loads 23 tools, `system_administrator` 55, `platform_developer` 41, `portal_developer` 35, `integration_engineer` 29, `devops_engineer` 24, and more
- A setup wizard, `npx nowaikit setup`, that detects your installed AI clients and writes their configuration
Node.js 20+ and `npm install -g nowaikit`. `SERVICENOW_INSTANCE_URL` and `SERVICENOW_AUTH_METHOD` are required; basic auth adds `SERVICENOW_BASIC_USERNAME` and `SERVICENOW_BASIC_PASSWORD`, and OAuth has its own setup guide. Writes stay off until you set `WRITE_ENABLED`, scripting until `SCRIPTING_ENABLED`, CMDB changes until `CMDB_WRITE_ENABLED`, and ATF tools until `ATF_ENABLED`. No instance? ServiceNow gives out free Personal Developer Instances.
One command plus a key — npm install -g nowaikit, then supply credentials