A
licenseA
qualityD
maintenanceAn 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.
22
MIT
servicenow-mcp-ai
by IvanBBaev
Related Servers
Alternatives to servicenow-mcp-ai
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
- AlicenseCqualityBmaintenanceMCP server enabling interaction with ServiceNow API for managing incidents, CMDB, change management, and other ServiceNow operations via natural language.13320MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing CRUD tools for ServiceNow business rules, client scripts, and script includes.-
- AlicenseAqualityDmaintenanceMCP server for ServiceNow that exposes Table, Aggregate, and schema APIs as tools with a write gate protecting against unintended modifications.538 npmMIT
- AlicenseAqualityDmaintenanceThe most comprehensive ServiceNow MCP server. 17 tools for full CRUD, CMDB graph traversal, background scripts, ATF testing, and more.17135 npm13MIT
TDQS
A3.6/5.0
Scored across 20 tools
Disambiguation4/5
Most tools map to a single clear resource+action (query_table vs get_record, create/update/upsert/delete are well-differentiated by their descriptions, including the AMBIGUOUS_KEY/STALE_RECORD semantics of upsert). The only mild overlaps are in diagnostics (get_status vs test_connection vs check_capabilities) and package discovery (find_tools vs list_packages), but descriptions give enough signal to pick correctly.
Naming Consistency5/5
Every tool follows the same servicenow_<verb>_<noun> snake_case convention (list_tables, describe_table, create_record, enable_package, test_connection). No camelCase or style mixing anywhere.
Tool Count4/5
20 tools is at the upper edge of the comfortable range but each earns its place across data access, connection/profile management, policy, and package administration. Slightly heavy, though the package-enable/disable mechanism keeps the active surface manageable.
Completeness4/5
Full record lifecycle (create/read/query/update/upsert/delete), schema introspection, aggregation, and solid connection/policy/diagnostic coverage make the surface fairly complete. Gaps remain around batch operations, attachments, and higher-level admin flows, but core ServiceNow workflows are covered.
Maintenance
ActivityActive
ResponsivenessUnresponsive