No user-submitted related servers found.
Scored across 28 tools
Most tools target a clearly distinct resource and action, and the descriptions explicitly separate similar areas such as deployment health vs. logs vs. run history. A few pairs could still be confused at a glance, notably run_workflow vs. call_deployed_workflow and list_workflows vs. list_deployed_tools, but the descriptions resolve them.
All 28 tools follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, deploy_, check_, etc.). Compound nouns like rotate_webhook_secret and get_deployment_status are still predictable and readable.
At 28 tools this is heavy for an agent-facing set and exceeds the typical comfortable range. The domain is genuinely broad—workflow authoring, deployment, monitoring, connections, and agent tools—so most tools earn their place, but some monitoring/run tools could likely be consolidated.
Coverage is strong: workflow CRUD, validation, deploy, versioning/rollback, run execution and control, logs/status, node schemas, setup/connections, file listing, webhook secret rotation, and deployed-tool discovery/calling. The main gap is that archiving is a dead end within MCP—there is no restore/unarchive or delete operation, requiring the user to go to the editor.