A
licenseC
qualityA
maintenanceEnables AI to interact with ServiceNow instances via MCP, providing 400+ tools across all modules for automation, development, and management.
500
805 npm
17
Elastic 2.0
servicenow-mcp
by aartiq
Related Servers
Alternatives to servicenow-mcp
Related Servers
- AlicenseAqualityDmaintenanceThe most comprehensive ServiceNow MCP server. 17 tools for full CRUD, CMDB graph traversal, background scripts, ATF testing, and more.17160 npm13MIT
- 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
- 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.1,291 npm53Apache 2.0
- AlicenseCqualityBmaintenanceEnables natural language control of ServiceNow from AI clients like Claude and Cursor. Provides 400+ tools for incidents, changes, CMDB, and scripts via MCP protocol.100286 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server providing 102 production-ready tools for Jira, Confluence, and Bitbucket, enabling AI agents to manage issues, pages, repositories, and more via natural language.1MIT
- AlicenseAqualityAmaintenanceAn MCP server that enables AI assistants to interact with ServiceNow instances, allowing script execution, data querying, ATF tests, and log tailing through natural language commands.8979 npm16MIT
TDQS
C2.7/5.0
Scored across 506 tools
Disambiguation1/5
With 506 tools, there is massive overlap: multiple query tools (query_records, fluent_query, fluent_sdk_query, nlq_query, natural_language_search, ai_search), multiple update-set tools (list_update_sets, list_changesets, get_changeset, commit_changeset, etc.), and many utility/search tools that blur together. Agents would frequently struggle to pick the correct tool.
Naming Consistency3/5
Most tools follow a snake_case verb_noun pattern, but the verbs are highly varied (get/list/create/update/add/run/trigger/execute/generate/validate/import/export/find/analyze) and some tools use noun-only or phrase names like change_readiness, service_health, natural_language_search, and fluent_build. The overall convention is readable but not uniform.
Tool Count1/5
506 tools is an extreme count for any MCP server, far beyond the 3-15 well-scoped range. The set feels like a full platform API dump rather than a curated, coherent toolset, with clear redundancy across domains.
Completeness3/5
Coverage is broad across many ServiceNow modules (ITSM, CSM, HRSD, CMDB, GRC, workflows, UI Builder, etc.), but there are notable gaps such as no list_problems, no delete operations for many core records, and no unified update for several artifact types. The generic query/update/delete tools mitigate these gaps but the domain-specific surface is uneven.
Maintenance
ActivityActive
ResponsivenessWithin a week