Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ServiceNow MCP Server Search for open incidents related to login issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This project hosts a Model Context Protocol (MCP) server that exposes ServiceNow ticket, knowledge base, and service catalog data over Streamable HTTP.
MCP tool | Purpose |
| Search |
| Read one ticket by |
| Search published |
| Search active |
| Read one catalog item by |
Related MCP server: ServiceNow MCP Server
Install dependencies:
npm installCopy .env.example to .env and set your ServiceNow instance and credentials:
Copy-Item .env.example .envStart the server:
npm run devThe MCP endpoint is:
http://localhost:3000/mcpUse a dedicated ServiceNow integration account or OAuth app with least-privilege read access to:
incident
problem
change_request
sc_request
sc_task
kb_knowledge
sc_cat_item
For production, prefer OAuth bearer tokens or a ServiceNow OAuth client flow over basic auth.
Set these variables first:
$RESOURCE_GROUP = "rg-servicenow-mcp"
$LOCATION = "centralindia"
$ACR_NAME = "acrsnowmcp$((Get-Random -Maximum 99999))"
$ENV_NAME = "cae-servicenow-mcp"
$APP_NAME = "servicenow-mcp"
$IMAGE_NAME = "servicenow-mcp-server:0.1.0"
$SERVICENOW_URL = "https://your-instance.service-now.com"
$SERVICENOW_USERNAME = "your-integration-user"
$SERVICENOW_PASSWORD = "your-password"Create Azure resources and build the image:
az group create --name $RESOURCE_GROUP --location $LOCATION
az acr create --resource-group $RESOURCE_GROUP --name $ACR_NAME --sku Basic --admin-enabled true
az acr build --registry $ACR_NAME --image $IMAGE_NAME .
az containerapp env create --name $ENV_NAME --resource-group $RESOURCE_GROUP --location $LOCATIONDeploy the container app:
$ACR_LOGIN_SERVER = az acr show --name $ACR_NAME --query loginServer -o tsv
$ACR_USERNAME = az acr credential show --name $ACR_NAME --query username -o tsv
$ACR_PASSWORD = az acr credential show --name $ACR_NAME --query "passwords[0].value" -o tsv
az containerapp create `
--name $APP_NAME `
--resource-group $RESOURCE_GROUP `
--environment $ENV_NAME `
--image "$ACR_LOGIN_SERVER/$IMAGE_NAME" `
--target-port 3000 `
--ingress external `
--registry-server $ACR_LOGIN_SERVER `
--registry-username $ACR_USERNAME `
--registry-password $ACR_PASSWORD `
--secrets `
servicenow-url=$SERVICENOW_URL `
servicenow-username=$SERVICENOW_USERNAME `
servicenow-password=$SERVICENOW_PASSWORD `
--env-vars `
SERVICENOW_INSTANCE_URL=secretref:servicenow-url `
SERVICENOW_USERNAME=secretref:servicenow-username `
SERVICENOW_PASSWORD=secretref:servicenow-passwordGet the public MCP URL:
$FQDN = az containerapp show --name $APP_NAME --resource-group $RESOURCE_GROUP --query properties.configuration.ingress.fqdn -o tsv
"https://$FQDN/mcp"Health check:
curl.exe "https://$FQDN/healthz"Replace the username/password secret and environment variable lines with:
--secrets servicenow-url=$SERVICENOW_URL servicenow-oauth-token=$SERVICENOW_OAUTH_TOKEN `
--env-vars SERVICENOW_INSTANCE_URL=secretref:servicenow-url SERVICENOW_OAUTH_TOKEN=secretref:servicenow-oauth-tokenPut Azure API Management or an authenticated ingress in front of the MCP endpoint.
Restrict Container Apps ingress to your corporate network where possible.
Use Azure Key Vault secret references for ServiceNow credentials.
Create a dedicated ServiceNow integration user with read-only ACLs.
Add log analytics alerts for repeated ServiceNow API failures.
This server cannot be deployed
Connect AI agents to ProductNow's context engine to search, create, review, and act.
Make your knowledge agent-ready. One MCP endpoint, 5 connectors, 3 search modes.
Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.
Search your knowledge bases from any AI assistant using hybrid RAG.
