Servicenow Devtools MCP

What is Servicenow Devtools MCP?

Servicenow Devtools MCP is a developer- and debug-focused Model Context Protocol (MCP) server for ServiceNow. It gives AI agents direct access to a ServiceNow instance for introspection, debugging, change intelligence, ITIL process management, and documentation generation. The server provides 86 tools across 14 tool packages.

How to use Servicenow Devtools MCP?

Run directly with uvx servicenow-devtools-mcp after setting the required environment variables SERVICENOW_INSTANCE_URL, SERVICENOW_USERNAME, and SERVICENOW_PASSWORD (or use a .env file). Configure the server in any MCP client by specifying the command and environment variables. Optional variables control tool package selection, environment label (dev/test/staging/prod), row limits, and large table filters.

Key features of Servicenow Devtools MCP

• Instance introspection (describe tables, query records, compute aggregates)
• Relationship mapping (incoming/outgoing references for any record)
• Change intelligence (inspect update sets, diff artifact versions)
• Debug and trace (record timelines, flow executions, email chains)
• Record CRUD with preview-then-apply pattern
• 7 built-in investigation modules (stale automations, ACL conflicts, etc.)
• Safety guardrails (table deny lists, field masking, write gating in production)

Use cases of Servicenow Devtools MCP

• Debug and trace ServiceNow record changes, flow executions, and integration errors
• Manage incidents, change requests, problems, and service requests via AI
• Generate documentation (logic maps, test scenarios, code review notes)
• Browse CMDB configuration items, relationships, and health checks
• Order from Service Catalog and manage shopping cart through natural language

FAQ from Servicenow Devtools MCP

What runtime does Servicenow Devtools MCP require?

It requires Python and is run via uvx (no installation needed). The uv tool must be available.

Where do my data and credentials reside?

All data stays within your ServiceNow instance. Credentials are passed as environment variables and are never stored by the server.

How does the server authenticate with ServiceNow?

It uses Basic Authentication via SERVICENOW_USERNAME and SERVICENOW_PASSWORD. The instance URL must start with https://.

What safety protections are included?

Write operations are blocked when SERVICENOW_ENV is set to "prod" or "production". Sensitive tables (e.g., sys_user_has_role) are deny-listed, sensitive fields are masked, and row limits are capped (default 100, max 10,000). Large tables require date-bounded queries.

What transport does the server use?

It uses stdio transport (no HTTP server). Configuration examples are provided for OpenCode, Claude Desktop, and VS Code/Cursor.