Servicenow MCP Server

Servicenow MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Servicenow MCP directly instead of describing what you should do. A Model Completion Protocol (MCP) server implementation for ServiceNow, allowing Claude to interact with ServiceNow instances.

What you get

This project implements an MCP server that enables Claude to connect to ServiceNow instances, retrieve data, and perform actions through the ServiceNow API. It serves as a bridge between Claude and ServiceNow, allowing for seamless integration.

• Connect to ServiceNow instances using various authentication methods (Basic, OAuth, API Key)
• Query ServiceNow records and tables
• Create, update, and delete ServiceNow records
• Execute ServiceNow scripts and workflows
• Access and query the ServiceNow Service Catalog
• Analyze and optimize the ServiceNow Service Catalog

What the assistant can call

Once Servicenow MCP is connected, these are the calls the assistant has available:

• Solution — Make sure you're passing a dictionary with the parameters, not a Pydantic model object
• Note — The change management tools have been updated to handle this error automatically. The functions will now attempt to unwrap parameters if they're
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — 1. Clone this repository: git clone https://github.com/yourusername/servicenow-mcp.git cd servicenow-mcp
• Example — See the examples/sse_server_example.py file for a complete example of setting up and running the SSE server
• Documentation — Additional documentation is available in the docs directory:
• Troubleshooting — The Troubleshooting tool exposed by this server
• Contributing — Contributions are welcome! Please feel free to submit a Pull Request

Configuration and credentials

You will need 8 environment variables: SERVICENOW_INSTANCE_URL, SERVICENOW_USERNAME, SERVICENOW_PASSWORD, SERVICENOW_AUTH_TYPE, SERVICENOW_CLIENT_ID, SERVICENOW_CLIENT_SECRET, SERVICENOW_TOKEN_URL, SERVICENOW_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.11 or higher - A ServiceNow instance with appropriate access credentials

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Servicenow MCP's toolset — Solution, Note, Prerequisites and 5 more — is a fair guide to whether it matches your workflow. It is maintained by shameerampcome; 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.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the servicenow mcp mcp server does with a few real requests.