ServiceNow PDI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOPE | Yes | The OAuth scope, e.g., useraccount | |
| PDI_URL | Yes | The ServiceNow Personal Developer Instance URL | |
| CLIENT_ID | Yes | The public OAuth client ID | |
| REDIRECT_URI | Yes | The redirect URI, must be http://127.0.0.1:33418 | |
| REFRESH_TOKEN | Yes | The refresh token saved from the authorization flow |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| servicenow_list_recordsC | List records from any ServiceNow table using an optional encoded query and field list. |
| servicenow_get_recordA | Retrieve one record from any ServiceNow table by sys_id. |
| servicenow_create_recordC | Create a record in any ServiceNow table. |
| servicenow_update_recordC | Update a record in any ServiceNow table by sys_id. |
| servicenow_delete_recordB | Delete one record from any ServiceNow table by sys_id. |
| servicenow_test_connectionA | Verify OAuth access to a ServiceNow PDI and return a small sample from sys_properties. |
| servicenow_create_flowC | Create a ServiceNow Flow record in sys_hub_flow. |
| servicenow_get_flowC | Retrieve one ServiceNow Flow record by sys_id. |
| servicenow_update_flowC | Update one ServiceNow Flow record by sys_id. |
| servicenow_delete_flowB | Delete one ServiceNow Flow record by sys_id. |
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 10 tools
Each tool targets a distinct resource and action: record operations are for any table, flow operations are specifically for sys_hub_flow, and test_connection is a diagnostic. The boundaries between tools are clear and unlikely to be confused.
All tool names follow a consistent verb_noun pattern with a 'servicenow_' prefix, e.g., servicenow_list_records, servicenow_create_flow. This predictable structure makes the set easy to navigate.
Ten tools provide comprehensive coverage for generic record operations and specialized flow operations without unnecessary bloat. The count is well-scoped for a ServiceNow integration.
The server offers complete CRUD for records and flows, plus connection testing, covering core lifecycle operations. However, it lacks bulk operations, attachment handling, or advanced query features that might be needed for full ServiceNow automation.