servicenow-api
Related Servers
Alternatives to servicenow-api
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server to interact with ServiceNow instances, enabling ITSM, CMDB, workflow, and knowledge search operations.MIT
- FlicenseAqualityCmaintenanceA ServiceNow MCP server that enables natural language management of incidents via the Table API, with tools to create, read, update, search, comment on, and resolve incidents.6-
- AlicenseAqualityDmaintenanceEnables natural language interaction with ServiceNow instances for managing incidents, changes, CMDB, service catalog, users, groups, and knowledge base via MCP.413 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server for interacting with a ServiceNow instance via its Table API, enabling CRUD operations on incident, request, and requested item tables, as well as generic operations on any table by name.22MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables LLMs to interact with ServiceNow instances for managing incidents, users, stories, workflows, knowledge base articles, and script includes via the FastMCP framework.-
- AlicenseAqualityAmaintenanceAn MCP server that enables AI assistants to interact with ServiceNow instances, allowing script execution, data querying, ATF tests, and log tailing through natural language commands.8935 npm16MIT
TDQS
Scored across 133 tools
Many tools overlap heavily: generic table CRUD tools (add/get/patch/update/delete_table_record) duplicate entity-specific incident, problem, and change request operations, while servicenow_api_request and servicenow_batch_request are broad escape hatches. Numerous tools such as 'Invoke the ... operation' lack enough description to distinguish their boundaries, making misselection likely despite some clearly distinct domains.
Most tool names use the servicenow_ prefix and snake_case verb_noun structure (e.g., get_incident, create_change_request, delete_problem), which is readable. However, there are notable deviations such as noun-only or vague names (servicenow_progress, servicenow_full_scan, servicenow_metricbase_insert) and inconsistent singular/plural/alias patterns that reduce predictability.
133 tools is an extreme mismatch for a coherent MCP server surface; the recommended well-scoped range is typically 3-15 tools. The count is inflated by many redundant wrappers, generic table operations, and fine-grained SDK/administrative actions that likely belong in fewer, more parameterized tools.
The surface covers a broad range of ServiceNow domains: incidents, problems, change management, CMDB, knowledge, DevOps, app repository, plugins, update sets, import sets, scanning, attachments, and SDK lifecycle. Some entity-specific gaps remain, such as knowledge article write operations and CI instance deletion, but the generic table CRUD and api_request tools provide workarounds for many missing operations.