No user-submitted related servers found.
Scored across 19 tools
Multiple read/state tools (list, get, status, watch, watches, browser_result, doctor) have overlapping 'read local state or monitoring results' purposes, and browser_run vs submit can both lead to generation. The descriptions do help distinguish them, but an agent still faces several near-boundary choices.
All tools share the workbench_ prefix and snake_case, which gives a readable family feel. However, the naming convention is mixed: some are verb_noun like browser_start and prepare_feature, while others are bare nouns or verbs like list, get, watches, assets, capabilities, and doctor.
At 19 tools, the server is in the borderline-heavy range. Most tools map to a real workflow stage, but several status/watch/result variants could likely be consolidated.
The server covers the core generate-monitor-download-archive lifecycle, including recovery, manual ingest, diagnostics, and basic Blender integration. Minor gaps exist around cancellation and cleanup/delete operations, but the intended workflow has no obvious dead ends.