Skip to main content
Glama

Related Servers

Alternatives to @onlyflows/servicenow-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      The 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.
      500
      4,607 npm
      237
      Elastic 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      20
      258 npm
      12
      GPL 3.0
    • F
      license
      B
      quality
      A
      maintenance
      An 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.
      32
      2
      -

    TDQS

    A3.6/5.0

    Scored across 24 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityActive
    ResponsivenessLimited data