MCP Server for ServiceNow

What is MCP Server for ServiceNow?

MCP Server for ServiceNow is a generic, modular, and extensible MCP integration that exposes ServiceNow capabilities as tools for AI agents and external systems. It covers ITSM, ITOM, SAM, HAM, Enhanced CMDB, PPM, Employee Experience, Reporting, Analytics, dynamic tool registration, and workflow orchestration.

How to use MCP Server for ServiceNow?

Clone the repository, create a Python 3.7+ virtual environment, install dependencies (requests, fastapi, uvicorn, MCP SDK), set your ServiceNow instance URL and authentication method (basic or OAuth) in config.py, then run python main.py to start the server using standard I/O transport. Tools are invoked by sending JSON payloads specifying the tool name and arguments.

Key features of MCP Server for ServiceNow

• Generic ServiceNow client with CRUD, queries, Basic & OAuth auth.
• Modular architecture with separate domain modules (ITSM, ITOM, etc.).
• Enhanced CMDB with validation, deduplication, relationship management, enrichment, and audit logging.
• Dynamic tool registration, deregistration, and listing at runtime.
• Workflow orchestration for coordinating complex multi-step processes.
• Rich, configurable prompt templates for AI agent interactions.

Use cases of MCP Server for ServiceNow

• Automate incident management (create, read, update, delete incidents) via AI agents.
• Manage asset lifecycle (SAM license records, HAM asset records) from external orchestration tools.
• Perform enhanced CMDB operations (create/query CI records, deduplicate, manage relationships, enrich data).
• Trigger ITOM events and manage PPM projects through API-driven workflows.
• Orchestrate multi-step access provisioning or other business processes using the workflow module.

FAQ from MCP Server for ServiceNow

What authentication methods are supported?

The server supports both Basic Authentication and OAuth. Set SN_AUTH_METHOD in config.py to either "basic" or "oauth" and provide the corresponding credentials.

What are the runtime requirements?

Python 3.7 or higher is required, along with the packages requests, fastapi, uvicorn, and the MCP SDK.

How are tools invoked?

Tools are invoked by sending a JSON payload with a name field (the tool name) and an arguments object matching the tool’s input schema. The server uses standard I/O transport for development and testing.

Does the server support dynamic tool registration?

Yes, the dynamic_tools module allows registration, deregistration, and listing of new tools at runtime without server restart.

What is the default transport?

The MCP server uses standard I/O transport when started via python main.py, making it suitable for development and testing with MCP-compatible clients.