mfa-servicenow-mcp
Related Servers
Alternatives to mfa-servicenow-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server providing CRUD tools for ServiceNow business rules, client scripts, and script includes.-
- AlicenseAqualityBmaintenanceMCP server for ServiceNow that exposes Table, Aggregate, and schema APIs as tools with a write gate protecting against unintended modifications.515 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server to interact with ServiceNow instances, enabling ITSM, CMDB, workflow, and knowledge search operations.MIT
- AlicenseAqualityDmaintenanceThe most comprehensive ServiceNow MCP server. 17 tools for full CRUD, CMDB graph traversal, background scripts, ATF testing, and more.17160 npm13MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives Claude Code tools to read, write, and configure a ServiceNow instance, enabling hands-off flow design and management via basic auth.53 npmMIT
- AlicenseAqualityAmaintenanceAn 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.1968 npm8MIT
TDQS
Scored across 32 tools
Several clusters overlap: get_widget_bundle, get_portal_component_code, and get_metadata_source all fetch source/body; search_server_code vs search_portal_regex_matches vs query_local_graph all search; download_portal_sources vs download_app_sources both download. Descriptions work hard to draw boundaries ('last resort', 'LEGACY ONLY', 'portal only'), which mitigates but does not eliminate misselection risk.
Most tools follow a verb_noun pattern (get_page, download_attachment, verify_deployment_xml), but the sn_-prefixed namespace tools (sn_health, sn_query, sn_schema, sn_discover) mix a noun-prefix convention with the rest. Readable overall, but conventions are mixed rather than uniform.
At 32 tools this is heavy and well past the 25-tool threshold, with several near-duplicate source-fetching and search tools that could be consolidated. The domain is complex enough to justify a large surface, but the set is over-scoped from a coherence standpoint.
Coverage is strong: discovery, CRUD for Scripted REST/script includes/widget dependencies, flow and workflow editing, portal/widget lifecycle, deployment XML export/verify, and offline auditing. Minor gaps exist (e.g. no explicit update-set or user/role management), but core ServiceNow dev workflows are well covered.