ServiceNow Incidents MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVICENOW_TOKEN | No | Pre-obtained access token, required for bearer auth | |
| SERVICENOW_PASSWORD | No | Password, required for basic auth | |
| SERVICENOW_USERNAME | No | Integration username, required for basic auth | |
| SERVICENOW_AUTH_TYPE | No | Authentication type, defaults to basic | |
| SERVICENOW_INSTANCE_URL | Yes | HTTPS instance URL, e.g. https://your-instance.service-now.com without /api | |
| SERVICENOW_TIMEOUT_SECONDS | No | Network timeout in seconds, default 30, greater than 0 and at most 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_incidentsA | Lista incidentes com encoded query ServiceNow, campos e paginação explícita. Exemplo de query: active=true^priority=1^ORDERBYsys_id. Páginas vazias podem ocorrer por ACL; use next_offset/total quando disponíveis. |
| get_incidentA | Obtém um incidente por sys_id ou número INC; fields limita os campos retornados. |
| create_incidentA | Cria incidente; fields aceita description, impact, urgency, caller_id e campos u_*. Referências devem usar sys_id. Campos extras obrigatórios dependem da instância. Não permite number ou sys_*. Não repita automaticamente após falha de comunicação. |
| update_incidentB | Altera apenas os campos fornecidos via PATCH, incluindo campos personalizados. Exige fields não vazio. Não permite number ou sys_*. Para resolução, envie state e os campos exigidos pela instância; não há conversão automática de nomes de estados. |
| add_incident_commentA | Adiciona comentário (comments) ou nota interna (work_notes), com seleção obrigatória. A visibilidade segue a configuração da instância. Repetir pode duplicar a entrada. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action and resource: listing, fetching, creating, updating, and commenting on incidents. The add_incident_comment tool is clearly separated from update_incident by its specific purpose of adding comments or work notes.
Tool names consistently follow a verb_noun pattern: list_incidents, get_incident, create_incident, update_incident, add_incident_comment. The only mild deviation is the wider verb 'add' for comments, but it still fits the convention.
Five tools is well-scoped for a ServiceNow incidents server, covering the core incident workflow without unnecessary bloat. Each tool earns its place and the count is appropriate for the domain.
The server provides solid lifecycle coverage with list, get, create, update, and comment operations. Missing delete is acceptable for incident management, though there is no direct way to retrieve existing comments/work notes, which is a minor gap.