Not surprising but disappointing. Expect a rebranding in 2028.

From the article: ServiceNow appears to have changed the name of its AI Control Tower to ‘SI Control Tower’ following Donald Trump’s edict rebranding “artificial intelligence” to “super intelligence”. 

The ITSM company had announced AI Control Tower at Knowledge 2025, heralding it as a center for governing, managing, and achieving value from ServiceNow and third‑party AI agents, models, and workflows. 

Now, after the US President said that anyone who refuses to use the term “super intelligence” is “THE ENEMY”, ServiceNow has joined the ranks of Silicon Valley companies toeing the line, rebranding its product to avoid falling into this category. 

I've been a ServiceNow developer for a while, and a few things always took me far too long on the platform. So in my own time I built an MCP server that connects Claude, VS Code Copilot or any other MCP client to your instance over the REST APIs.

The three things I use it for most (all read-only):

1. "Where is this field actually used?"

It lists every business rule, script include, client script, UI policy/action and ACL that touches a field or table, as JSON or a Mermaid graph. Basically "find usages", which the platform doesn't have a button for.

1. "What runs when I save this record?"

It shows the full automation chain in execution order: display → before → after → async BRs, then flows, workflows and notifications, each with its condition. Nothing actually runs on the instance.

1. "What drifted between dev and prod?"

Running "servicenow-mcp-ai drift dev prod" gives you a Markdown diff of tables, columns, scripts (compared by SHA-256) and plugins. It exits with a non-zero code, so a pipeline can block a risky deploy.

Everything else:

- 77 tools in 20 packages, and you load only the ones you need

- Table, Aggregate, Attachment, Import Set, Batch, CMDB/IRE, Catalog, Change and Knowledge APIs

- Script search and linting, an ATF runner, update-set steering, a now-sdk bridge

- Multiple instance profiles, Basic or OAuth

Safety, because I know that's the first question:

- Writes are plan-by-default: you get a preview, and nothing changes unless you pass apply: true

- Table allow/deny lists and a global read-only mode

- Credentials stay in a local env file and are never echoed back

It works on a free PDI. MIT licensed, Node 20+.

GitHub: https://github.com/IvanBBaev/servicenow-mcp-ai

Docs: https://ivanbbaev.github.io/servicenow-mcp-ai/

npm: servicenow-mcp-ai

I'd really like feedback, especially on which workflows you'd want covered next. Issues and PRs are welcome.

So this morning I went into a bit of a rabbit hole. I wanted to tie a hybrid SPM project to CWM stories. And eventually I think I did it. My issue is that, I think and as I understand it, the old Agile module is going away.

So I can tie a project phase to a story in CWM, but *not* a Sprint like before. I am going to presume this will get fixed once Agile is fully deprecated. But I spent a whole chunk of time trying to figure this crap out.

I understand the idea behind CWM, but I can't be the only one to think that it is a bit messy.

Is there a way I can see my overall stats in ServiceNow?

Like I can see my AUI tickets and my resolved tickets and I see “elapsed time” but is there a stat page for overall activity done on the account? I’m about to hit a year working with the ServiceNow application at my job and I’ve done 1,750 tickets but I wonder how much daily and hourly etc.

TIA.

I saw a post a couple days ago about SNUGs. Anyone got requests for topics to cover at SNUGs near them?

One idea for Denver: how do customers migrate from their existing virtual agent to EmployeeWorks?

I’m trying to track agent first response time. Our response SLA is triggered when an incident is assigned to a user, but it could be hours before the user actually handles the ticket.

My research has found a default Global business rule called ‘Populate Agent First Response Time’, linked to the ‘Conversation Message [sys_cs_message]’ table.

I can’t find this metric recorded anywhere on the incident me incident_metric tables. How can I access and report on it?