ServiceNow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVICENOW_API_KEY | No | Your ServiceNow API key | |
| SERVICENOW_PASSWORD | No | Your ServiceNow password | |
| SERVICENOW_USERNAME | No | Your ServiceNow username | |
| SERVICENOW_AUTH_TYPE | No | Authentication type (basic, oauth, or api_key) | basic |
| SERVICENOW_CLIENT_ID | No | Your ServiceNow OAuth client ID | |
| SERVICENOW_TOKEN_URL | No | The OAuth token URL for your ServiceNow instance | |
| SERVICENOW_INSTANCE_URL | Yes | The URL of your ServiceNow instance | |
| SERVICENOW_CLIENT_SECRET | No | Your ServiceNow OAuth client secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_incidentC | Create a new incident in ServiceNow |
| update_incidentC | Update an existing incident in ServiceNow |
| add_commentB | Add a comment to an incident in ServiceNow |
| resolve_incidentC | Resolve an incident in ServiceNow |
| list_incidentsC | List incidents from ServiceNow |
| list_catalog_itemsB | List service catalog items. |
| get_catalog_itemC | Get a specific service catalog item. |
| list_catalog_categoriesC | List service catalog categories. |
| create_catalog_categoryC | Create a new service catalog category. |
| update_catalog_categoryC | Update an existing service catalog category. |
| move_catalog_itemsC | Move catalog items to a different category. |
| get_optimization_recommendationsC | Get optimization recommendations for the service catalog. |
| update_catalog_itemC | Update a service catalog item. |
| create_change_requestC | Create a new change request in ServiceNow |
| update_change_requestC | Update an existing change request in ServiceNow |
| list_change_requestsC | List change requests from ServiceNow |
| get_change_request_detailsC | Get detailed information about a specific change request |
| add_change_taskC | Add a task to a change request |
| submit_change_for_approvalC | Submit a change request for approval |
| approve_changeC | Approve a change request |
| reject_changeD | Reject a change request |
| list_workflowsC | List workflows from ServiceNow |
| get_workflow_detailsC | Get detailed information about a specific workflow |
| list_workflow_versionsC | List workflow versions from ServiceNow |
| get_workflow_activitiesC | Get activities for a specific workflow |
| create_workflowC | Create a new workflow in ServiceNow |
| update_workflowC | Update an existing workflow in ServiceNow |
| activate_workflowC | Activate a workflow in ServiceNow |
| deactivate_workflowC | Deactivate a workflow in ServiceNow |
| add_workflow_activityC | Add a new activity to a workflow in ServiceNow |
| update_workflow_activityC | Update an existing activity in a workflow |
| delete_workflow_activityC | Delete an activity from a workflow |
| reorder_workflow_activitiesC | Reorder activities in a workflow |
| list_changesetsC | List changesets from ServiceNow |
| get_changeset_detailsC | Get detailed information about a specific changeset |
| create_changesetC | Create a new changeset in ServiceNow |
| update_changesetC | Update an existing changeset in ServiceNow |
| commit_changesetC | Commit a changeset in ServiceNow |
| publish_changesetC | Publish a changeset in ServiceNow |
| add_file_to_changesetC | Add a file to a changeset in ServiceNow |
| list_script_includesC | List script includes from ServiceNow |
| get_script_includeC | Get a specific script include from ServiceNow |
| create_script_includeC | Create a new script include in ServiceNow |
| update_script_includeC | Update an existing script include in ServiceNow |
| delete_script_includeD | – |
| create_knowledge_baseC | Create a new knowledge base in ServiceNow |
| list_knowledge_basesC | List knowledge bases from ServiceNow |
| create_categoryC | Create a new category in a knowledge base |
| create_articleC | Create a new knowledge article |
| update_articleC | Update an existing knowledge article |
| publish_articleD | Publish a knowledge article |
| list_articlesD | List knowledge articles |
| get_articleC | Get a specific knowledge article by ID |
| list_categoriesC | List categories in a knowledge base |
| create_userD | – |
| update_userD | – |
| get_userD | – |
| list_usersD | – |
| create_groupD | – |
| update_groupD | – |
| add_group_membersD | – |
| remove_group_membersD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| incidents://list | |
| catalog://items | |
| catalog://categories | |
| changesets://list | |
| scriptincludes://list |
TDQS
Scored across 62 tools
Most tools have distinct purposes targeting specific ServiceNow resources and actions, with clear boundaries between different domains like incidents, change requests, workflows, and knowledge articles. However, there is some potential overlap in generic CRUD operations across domains (e.g., create/update for different resources follow similar patterns), and a few tools like 'add_group_members' and 'remove_group_members' lack descriptions, which could cause minor confusion.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_incident', 'list_change_requests', and 'update_workflow'. All tools use snake_case without deviation, and verbs like create, get, list, update, delete, add, remove, approve, and reject are applied predictably across resources, making the naming scheme very readable and systematic.
With 62 tools, the count is excessive for a single server, leading to cognitive overload and potential inefficiency for agents. While ServiceNow is a broad platform, this many tools suggests over-fragmentation of operations that could be consolidated or scoped into multiple focused servers, making it borderline overwhelming for typical agent workflows.
The tool set provides comprehensive coverage of ServiceNow domains, including incidents, change requests, workflows, knowledge bases, catalog items, and user/group management. It supports full CRUD operations, lifecycle actions (e.g., approve, reject, publish, resolve), and specialized functions like reordering activities, ensuring agents can handle end-to-end processes without significant gaps.