ServiceNow MCP Server
Click on "Install 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 ServerSearch 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.
ServiceNow MCP Server on Azure Container Apps
This project hosts a Model Context Protocol (MCP) server that exposes ServiceNow ticket, knowledge base, and service catalog data over Streamable HTTP.
Tools exposed
MCP tool | Purpose |
| Search |
| Read one ticket by |
| Search published |
| Search active |
| Read one catalog item by |
Related MCP server: ServiceNow MCP Server
Local setup
Install dependencies:
npm installCopy
.env.exampleto.envand set your ServiceNow instance and credentials:Copy-Item .env.example .envStart the server:
npm run devThe MCP endpoint is:
http://localhost:3000/mcp
ServiceNow permissions
Use a dedicated ServiceNow integration account or OAuth app with least-privilege read access to:
incidentproblemchange_requestsc_requestsc_taskkb_knowledgesc_cat_item
For production, prefer OAuth bearer tokens or a ServiceNow OAuth client flow over basic auth.
Deploy to Azure Container Apps
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"Use OAuth token instead of basic auth
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-tokenProduction hardening
Put 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 installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceA Model Context Protocol server enabling AI agents to access and manipulate ServiceNow data through natural language interactions, allowing users to search for records, update them, and manage scripts.46MIT
- Alicense-qualityDmaintenanceA Model Context Protocol server that enables AI assistants and development tools to interact with ServiceNow instances, providing comprehensive API coverage for incident management, change management, CMDB, and other ServiceNow modules.3MIT
- Alicense-qualityDmaintenanceEnables authenticated interaction with ServiceNow via its REST API using per-user OAuth 2.0 tokens. It provides tools for managing incidents, tasks, knowledge articles, and service catalog requests while maintaining user-specific permissions.314MIT
- AlicenseAqualityDmaintenanceEnables natural language interaction with ServiceNow instances for managing incidents, changes, CMDB, service catalog, users, groups, and knowledge base via MCP.4145MIT
Related MCP Connectors
Connect to Atlassian Jira, Confluence, and Compass to search, create, and manage your work.
Search your knowledge bases from any AI assistant using hybrid RAG.
Search your Obsidian vault to quickly find notes by title or keyword, summarize related content, a…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prateek9920/servicenow-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server