No user-submitted related servers found.
Scored across 66 tools
Descriptions do a lot of explicit steering ("use download_generation for results", "for how many credits use account_overview"), but there is real overlap: prepare_generation vs prepare_run vs prepare_prompt_enhancement, cleanup_approve vs cleanup_approve_files, and generic api_read/api_write vs every dedicated tool all target the same underlying actions. The 11-tool cleanup pipeline and the media cluster (media, media_access, ensure_media, download_media, download_generation) require careful reading to pick correctly.
A uniform neurover_ prefix and snake_case keep it readable, but the verb/noun ordering is inconsistent: verb-first (create_workflow, delete_node, connect_nodes) mixed with noun-first (workflow_graph, model_settings, node_cancel, media_access, account_setup) and bare nouns (accounts, models, balance, audit). The outcome is mixed conventions that still parse but offer no predictable pattern.
66 tools is far beyond what the domain needs in one surface; the cleanup subsystem alone contributes 11 tools for one maintenance task. Auth (7) and update/diagnostics (3) further inflate the set, so an agent must navigate a very heavy tool list for routine generation work.
Coverage is genuinely broad: auth lifecycle, workflow and node CRUD, edges, the full prepare/submit/wait/download generation pipeline, media library management, dedup cleanup, billing, diagnostics, and generic API escape hatches for anything missing. Only minor gaps remain (e.g. no media rename/move or workflow export), and the generic API tools let agents work around them.