servicenow

servicenow-mcp is a comprehensive MCP server designed to integrate ServiceNow capabilities with a wide range of AI agents via the Model Context Protocol. It exposes a rich set of tools that cover Incident Management, Change Management, Scripting, ATF testing, Knowledge Management, Service Portal interactions, REST integrations, and more across multiple ServiceNow domains. Once the server is running, you can connect Claude, ChatGPT, Gemini, Cursor, Copilot, and other MCP-compatible clients to the same instance, enabling multi-agent collaboration, cross-environment queries, and autonomous workflows across dev, staging, and prod tenants. The server supports role-based tool packages and a large toolbox of automation capabilities, from creating incidents and runscripts to deploying ATF suites and orchestrating multi-step processes across customer tenants.

To use the tools, configure your MCP client to point at this server and select the desired tool packages relevant to your role (e.g., platform developer, service desk, MSP). You can switch between multiple ServiceNow environments within a session, run Now Assist workflows, and trigger agentic playbooks. For best results, ensure your AI agent is authenticated with the appropriate ServiceNow credentials and that instance references (like instance: "acme_prod") are provided when necessary to scope actions to a particular environment.

Prerequisites:

• Node.js 20.x or higher installed on the host
• Access to a compatible ServiceNow instance(s) for testing
• A Git repository containing the servicenow-mcp server code (as in this README project)

Installation steps:

1. Install dependencies

   • npm install

2. Build (if your workflow requires building TypeScript to JavaScript)

   • npm run build

3. Run the MCP server

   • npm start (Alternatively, run directly: node dist/server.js if you are using a prebuilt bundle)

4. Configure your MCP client

   • Point the client to http(s)://<host>:<port> as the MCP server endpoint
   • Authenticate as needed and select the ServiceNow tool packages you wish to enable

5. Verify connectivity

   • Use the client to fetch a tool reference or run a lightweight test like querying a basic Incident or Knowledge Article to confirm integration.

Tips and common considerations:

• Ensure your ServiceNow instances are accessible from the MCP server host (network allowlists, VPNs, and proper API permissions).
• Enable and test Now Assist and Agentic Playbooks where applicable to unlock autonomous automation features.
• Use multi-instance capabilities to compare environments side-by-side by passing instance identifiers on tool calls.
• If you encounter authentication issues, verify OAuth/Basic auth configurations in both the MCP server and the ServiceNow instance settings.
• Keep the MCP server updated with the latest tool packages and bug fixes to ensure compatibility with new ServiceNow APIs.
• Environment variables can be used to toggle feature flags, switch instances, or set credentials securely; consider documenting and versioning these in a secure config management system.
• For troubleshooting, refer to the docs in docs/MULTI_INSTANCE.md, docs/NOW_ASSIST.md, and ATF guidance in docs/ATF.md.