servicenow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVICENOW_INSTANCE | Yes | The ServiceNow instance name only (e.g. 'dev12345' for 'dev12345.service-now.com') | |
| SERVICENOW_PASSWORD | Yes | Password for basic auth credentials for a user with access to the incident table | |
| SERVICENOW_USERNAME | Yes | Username for basic auth credentials for a user with access to the incident table |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_incidentA | Create a new ServiceNow incident. Args: short_description: Brief summary of the incident (required). description: Full description of the issue. urgency: "1" (High), "2" (Medium), or "3" (Low). impact: "1" (High), "2" (Medium), or "3" (Low). category: Incident category, e.g. "software", "hardware", "network". assignment_group: Name or sys_id of the assignment group. caller_id: Name or sys_id of the user reporting the incident. |
| get_incidentA | Fetch a ServiceNow incident by its number (e.g. INC0010023) or sys_id. |
| update_incidentA | Update fields on an existing incident. Args: number_or_sys_id: Incident number (e.g. INC0010023) or sys_id. fields: Field name -> new value, e.g. {"state": "2", "priority": "1"}. |
| search_incidentsA | Search incidents using a ServiceNow encoded query. Args: query: ServiceNow encoded query string (sysparm_query), e.g. "active=true^priority=1" or "assigned_to.nameLIKEJohn". Leave empty to list the most recent incidents. limit: Max number of records to return (default 10). offset: Number of records to skip, for pagination. |
| add_commentA | Add a customer-visible comment or an internal work note to an incident. Args: number_or_sys_id: Incident number or sys_id. comment: Text to add. work_note: If True, adds as an internal work note instead of a customer-visible comment. |
| resolve_incidentB | Resolve an incident by setting its state to Resolved. Args: number_or_sys_id: Incident number or sys_id. close_notes: Notes describing the resolution. close_code: Resolution code, e.g. "Solved (Permanently)", "Solved (Workaround)". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_my_open_incidents | Prompt template: list open incidents reported by a given caller. Args: caller: The name, username, or sys_id of the person to look up as "me" (the incident's caller_id). The server authenticates as a service account, so it doesn't know who "me" is without this. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/siddhardhan/servicenow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server