ServiceNow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVICENOW_PASSWORD | No | Password for basic auth | |
| SERVICENOW_USERNAME | No | Username for basic auth | |
| SERVICENOW_AUTH_TYPE | Yes | Authentication type: 'basic' or 'oauth' | |
| SERVICENOW_CLIENT_ID | No | OAuth client ID (required if auth type is 'oauth') | |
| SERVICENOW_INSTANCE_URL | Yes | ServiceNow instance URL (e.g., https://your-instance.service-now.com) | |
| SERVICENOW_CLIENT_SECRET | No | OAuth client secret (required if auth type is 'oauth') |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_recordsA | List records from any ServiceNow table with optional filtering, field selection, and pagination |
| get_recordA | Get a single record from a ServiceNow table by sys_id |
| create_recordB | Create a new record in any ServiceNow table |
| update_recordA | Update an existing record in a ServiceNow table |
| delete_recordA | Delete a record from a ServiceNow table by sys_id |
| aggregate_recordsA | Aggregate records using COUNT, AVG, MIN, MAX, SUM with optional GROUP BY via the Stats API |
| list_ciA | List CMDB configuration items with optional class and query filtering |
| get_ciA | Get a single CMDB configuration item by sys_id |
| create_ciA | Create a new CMDB configuration item |
| update_ciC | Update a CMDB configuration item |
| get_ci_relationshipsA | Get relationships for a CMDB configuration item (parent and child) |
| get_system_propertiesB | Query ServiceNow system properties |
| get_current_userA | Get the currently authenticated user's information |
| get_table_schemaA | Get the data dictionary (field definitions) for a ServiceNow table, including inherited fields |
| list_update_setsA | List update sets with optional state and query filtering |
| get_update_setA | Get details of a specific update set by sys_id |
| create_update_setA | Create a new update set for tracking customizations |
| set_current_update_setA | Set an update set as the current active update set |
| list_update_set_changesA | List all customer updates (changes) within an update set |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| instance_info | Instance URL, platform version, logged-in user, and timezone |
| current_update_set | Currently active update set name, sys_id, and state |
| cmdb_classes | CMDB CI class hierarchy — class names, labels, and parent classes |
| query_syntax_help | ServiceNow encoded query operators reference — prevents hallucinated query syntax |
TDQS
Scored across 19 tools
Tools are mostly distinct, with clear separation between generic record operations and specialized update set/CI operations. Some potential overlap exists (e.g., list_records vs list_update_set_changes) but descriptions clarify intent.
All tools follow a consistent verb_noun pattern (create, set, list, get, update, delete, aggregate). Even complex nouns like update_set_changes maintain the pattern. No mixed conventions.
At 19 tools, the count is slightly above the typical 3-15 range but justified by covering generic record CRUD, update set lifecycle, CI management, and system utilities. Each tool serves a clear purpose, though a few could be merged without loss.
The service covers core CRUD for records, update sets, and CIs, plus schema, user, and property access. Minor gaps include lack of update set deletion and no mutation for CI relationships, but primary workflows are well supported.