No user-submitted related servers found.
Scored across 25 tools
Most tools have clearly distinct roles across the media pipeline: generation, design guidance, QA, compositing, post-processing, delivery, and cleanup. Some overlap exists between social_sizes, deliver, and media_optimize for resizing/compression, and between composition_check and design_audit for quality checks, but the descriptions make the intended stage and purpose reasonably clear.
All names use snake_case, which is good, but the structural pattern is mixed: some are noun_verb (image_generate, video_quote), some noun_noun (project_profile, design_brief), some verb_noun (background_remove, palette_extract), and some bare verbs (deliver, compose). The set remains readable, but an agent cannot rely on a predictable verb_noun convention.
At 25 tools this is borderline heavy for a single server, though the domain is broad and includes generation, design guidance, compositing, post-processing, delivery, account management, and cleanup. Most tools earn their place, but the count is high enough that the surface feels dense rather than tightly scoped.
The tool surface covers a full media asset lifecycle: provider/account setup, project profiling, design briefing and auditing, image/video generation with cost quotes, probing, background removal, palette extraction, compositing, resizing, optimization, delivery, video editing, cleanup, and usage reporting. There are no obvious dead ends for the stated no-api-media purpose.
