ServiceNow Dev MCP
Related Servers
Alternatives to ServiceNow Dev MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables Claude to interact with ServiceNow instances to manage incidents, service catalogs, workflows, and knowledge bases through the ServiceNow API. It supports comprehensive operations including record querying, script execution, and user management using various authentication methods.66MIT
- AlicenseCqualityDmaintenanceEnables Claude to interact with ServiceNow instances through comprehensive API integration. Supports incident management, service catalog operations, change requests, knowledge base management, user administration, and agile project management with multiple authentication methods.82MIT
- AlicenseBqualityNot gradedmaintenanceEnables Claude to interact with ServiceNow instances through the ServiceNow API. Supports comprehensive ServiceNow operations including incident management, service catalog management, change requests, user management, and workflow automation through natural language.82MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to interact with ServiceNow instances for incident management, service catalog operations, change requests, knowledge base management, user administration, and agile project workflows through various authentication methods.MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with ServiceNow instances through the ServiceNow API, supporting record management, service catalog operations, change management, and more via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with ServiceNow instances through the ServiceNow API, allowing data retrieval, record management, and workflow execution. Supports multiple authentication methods and tool packaging for role-based access control.MIT
TDQS
Scored across 125 tools
Each tool targets a specific resource and action, with clear phase prefixes (e.g., analyze_, build_, create_). Even within dense areas like migration, tools like discover_schema, build_artifacts, and run_full_migration are distinct. The platform prefixes (jira_, sf_, sn_) further separate concerns.
Tool names follow a consistent verb_noun pattern in snake_case. Platform-specific tools are uniformly prefixed (jira_, sf_, sn_). Variations like test_code_file or map_users still adhere to the same structure. No mixing of camelCase or inconsistent verb forms.
At 125 tools, the set is very large. While it covers a broad scope across multiple platforms (Jira, Salesforce, ServiceNow) and many functional areas (migration, testing, integration, code generation), the sheer number may overwhelm agents and increase selection complexity. Slight trimming or grouping could improve usability.
The tool surface is remarkably comprehensive, covering migration lifecycle, testing, integration, code review, and administration. Minor gaps exist: e.g., no direct tool for updating catalog items (only clone), and deletion tools are limited (e.g., no generic delete for most entities). Overall, core workflows are well-supported.