Skip to main content
Glama
tedorigawa001

ServiceNow-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ServiceNow-MCP

No user-submitted related servers found.

    Related Servers

    • snow-mcp

      ShunyaAI
      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

    • servicenow-platform-mcp

      Xerrion
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with ServiceNow through MCP, providing schema inspection, record CRUD, attachments, audit, Flow Designer, and platform investigations with policy-guarded access.
      15
      146 PyPI
      4
      MIT

    • ServiceNow MCP Server

      Deepakj22
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and development tools to interact with ServiceNow instances through the Model Context Protocol, supporting incident, change, problem, CMDB, service catalog, knowledge base, and custom table operations.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.8/5.0

    Scored across 376 tools

    Disambiguation2/5

    Many tools are clearly scoped, but there are direct overlaps: list_changesets/list_update_sets, get_virtual_agent_topics/list_va_topics_full, natural_language_search/nlq_query/ai_search, and check_table_completeness/analyze_data_quality. With 376 tools, an agent will frequently struggle to pick the intended one.

    Naming Consistency2/5

    The list/get/create/update convention is visible, but naming is inconsistent within the same domain: list_changesets vs list_update_sets, get_virtual_agent_topics (a list despite the get prefix), and mixed verbs like trigger_flow, run_transform_map, and execute_background_script. The use of changeset vs update_set and uib vs ux for similar concepts makes tool-name prediction unreliable.

    Tool Count1/5

    376 tools is an extreme scope for a single MCP server and flattens nearly the entire ServiceNow platform into one namespace. This overwhelms tool-selection and context budgets; the server should be split into focused domain servers like ITSM, CMDB, Portal, or Flow.

    Completeness3/5

    Coverage is broad across ITSM, HR, CSM, CMDB, flows, portals, and admin functions, but there are notable lifecycle gaps: create_flow exists without update_flow, create_subflow without update_subflow, and there is no dedicated list_incidents or list_problems beyond generic query_records. Update-set tooling is also split confusingly across changeset and update_set tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources