Servicenow Devtools MCP Server

Most developer tooling work still happens through a UI a human drives. Servicenow Devtools MCP MCP server moves it into the conversation instead. A comprehensive Model Context Protocol (MCP) server for ServiceNow. Provides 12 unified tools for platform introspection, change intelligence, debugging, record management, and automated investigations.

The short version

• Platform Introspection — - Describe table schemas with describe and query records with query using encoded queries
• Record Management — - Unified record_write and record_apply tools for create, update, and delete with a mandatory preview-then-apply safety pattern
• Attachment Operations — - Unified attachment for read operations and attachment_write for mutations
• Investigations — - Automated analysis of system health, stale automations, performance bottlenecks, and more via investigate
• Label Resolution — - Map human-readable choice labels to underlying values automatically with resolve_choice
• Service Catalog — - Dispatcher-based service_catalog tool for browsing and ordering

The tools it exposes

The server publishes 1 tool. What each one is for:

• OpenCode — The OpenCode tool exposed by this server

What it needs from you

Configuration is passed through the environment: SERVICENOW_INSTANCE_URL, SERVICENOW_USERNAME, SERVICENOW_PASSWORD, SENTRY_DSN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on PyPI as servicenow-platform-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Servicenow Devtools MCP's toolset — OpenCode — is a fair guide to whether it matches your workflow. It is maintained by xerrion; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.