Skip to main content
Glama
sn-mcp
by TaiRaven

Related Servers

Alternatives to sn-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to interact with a ServiceNow instance through thirteen consolidated tools covering records, schema, CMDB graph traversal, catalog, attachments, code, operations, knowledge, and administration, with a local store for notes, cache, saved queries, history, and revertible writes.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query ServiceNow incidents and to query, summarize, create, and update change_request records, plus search and create Method of Procedure records, using natural language. It runs locally over stdio/CLI or as a remote multi-user HTTP server that passes each user's credentials through per request without storing them.
      Apache 2.0
    • F
      license
      B
      quality
      C
      maintenance
      Enables authenticated interaction with a ServiceNow Personal Developer Instance through OAuth 2.0, exposing tools to test connectivity and perform generic CRUD operations on any ServiceNow table plus flow management on the sys_hub_flow table.
      10
      -
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.
      7
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with read access to ServiceNow instances to aid in building and debugging applications. It enables users to query tables, retrieve specific records, and inspect table schemas using standard ServiceNow encoded query strings.
      -

    TDQS

    B3/5.0

    Scored across 52 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Even similar-sounding tools like create_catalog_category versus create_category are clearly separated by context in their descriptions. The report tools are also distinct from CRUD operations.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., list_incidents, create_incident, update_incident, get_incident_by_number). Minor deviations like create_category are still unambiguous due to domain context, and the overall style is uniform.

    Tool Count2/5

    With 52 tools, the server is heavily overloaded, even though it covers multiple ServiceNow domains. This exceeds the 25-tool threshold for 'too many' and risks making tool selection more complex. While the breadth justifies a higher count, the sheer number is excessive for coherence.

    Completeness4/5

    The tool surface covers full CRUD and lifecycle operations for most domains: incidents, users, groups, changesets, catalog, knowledge, and change requests. Minor gaps exist (no delete operations for several resources, no incident approval workflow), but these are acceptable and do not hinder core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues