@onlyflows/servicenow-mcp
Related Servers
Alternatives to @onlyflows/servicenow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceThe most advanced & comprehensive ServiceNow MCP server — 150+ production-ready tools across 17 modules (ITSM, ITOM, HRSD, CSM, SecOps, GRC, Agile, ATF, Flow Designer, Now Assist, and more). Supports multi-instance management, four-tier permission control, 10 role-based tool packages, OAuth 2.0 + Basic Auth, and integrates with Claude, GPT-4o, Gemini, Cursor, VS Code, and Codex.5004,607 npm237Elastic 2.0
- AlicenseNot gradedqualityAmaintenanceA metadata-driven MCP server that auto-generates 480+ tools across 160+ ServiceNow tables, with multi-instance support, natural language search, and local script development.336 npm55Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server providing CRUD tools for ServiceNow business rules, client scripts, and script includes.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for ServiceNow that provides over 60 pre-built tools for ITSM, ITOM, and App Dev operations, enabling AI agents to manage incidents, changes, users, service catalog, and projects through a unified interface.6MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables running commands against a ServiceNow instance via its REST APIs, including Table, Aggregate, Attachment, Import Set, Batch, CMDB, Service Catalog, Change Management, and Knowledge APIs.20258 npm12GPL 3.0
- FlicenseBqualityAmaintenanceAn MCP server for ServiceNow that supports multi-factor authentication via real browser (Playwright) and provides tools for reading, writing, and managing ServiceNow artifacts with safety guards.322-
TDQS
Scored across 24 tools
The core CRUD set (sn_query/sn_get/sn_create/sn_update/sn_delete) is cleanly separated, and each specialty tool (sn_syslog, sn_relationships, sn_codesearch, sn_flow_view) targets a distinct artifact. The main ambiguity is sn_nl, a general natural-language interface that overlaps with sn_query, sn_aggregate, sn_schema, sn_create, sn_update, and sn_batch, and to a lesser degree sn_atf vs sn_atf_results both exposing ATF result reads — descriptions mitigate but do not eliminate this.
All 24 tools use a consistent `sn_` prefix with snake_case segments, giving a predictable namespace. Minor structural deviations exist between flat verb tools (sn_query), grouped families (sn_atf_readiness / sn_atf_author / sn_atf_run / sn_atf_results alongside a bare sn_atf), and resource-scoped names (sn_incident_add_comment), but none are confusing.
24 tools sits at the high end of the comfortable range, but ServiceNow is a genuinely broad platform (records, CMDB, ATF, flows, logs, attachments, discovery, profiles), so each tool maps to a real capability area rather than filler. A couple of niches (sn_incident_add_comment / sn_incident_add_work_note) could arguably fold into sn_update, but the surface is defensible.
Full record lifecycle is covered (query, get, create, update, delete, bulk batch, aggregates, schema), plus strong coverage of CMDB relationships, ATF authoring/running/results, code search, flow viewing, attachments, syslog, and instance health. Remaining gaps are modest: sn_attach cannot delete attachments, Flow Designer is read-only, and there is no explicit journal/history retrieval tool (only field-level comment appends).