Cutover MCP
OfficialRelated Servers
Alternatives to Cutover MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for the Runn API, enabling resource management and reporting through natural language.-

Keepit MCPofficial
AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Keepit backup and data protection services. Enables monitoring, management, and security operations through natural language.5MIT- AlicenseAqualityCmaintenanceMCP server that exposes Cleanuparr's REST API for inspecting status, history, statistics, jobs, and configuration, enabling natural language interaction with Cleanuparr.8MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP Server that enables natural language interaction with the Open Policy Agent REST API, allowing users to manage policies, decisions, and data through conversational interfaces.1-
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables Amazon Q CLI users to create, query, and manage Maverick sites through natural language commands.-
- AlicenseCqualityBmaintenanceAn MCP server that provides complete Kubernetes API operations, enabling cluster management, resource CRUD, diagnostics, backup/restore, and multi-cluster configuration via natural language.322MIT
TDQS
Scored across 45 tools
Most tools target distinct resource/action pairs, and the descriptions clarify boundaries between similar operations. There is only mild potential confusion between get_activities and get_action_logs, and between list/query variants for workspaces and runbook types.
Tool names are consistently snake_case and mostly follow a verb_noun pattern. Minor deviations include get_*_by_id versus get_stream/get_user, manage_runbook, and add_task_to_runbook, but the naming remains readable and predictable.
With 45 tools, the surface is heavy for a single server and exceeds the range where tools are easily scannable. Although the Cutover domain is broad, the many CRUD clusters for custom fields, groups, streams, and types increase selection burden significantly.
Core runbook, task, stream, comment, and custom-field workflows are well covered. However, there are notable gaps: no delete/archive runbook operation, no workspace update/delete, folders are list-only, users are read-only, and data-source tooling only provides an upload URL.