Skip to main content
Glama

Related Servers

Alternatives to vivid-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.6/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource plus action (generate_image vs generate_video vs generate_music vs generate_voice; analyze_product vs compare_product vs retouch), and paired read/create tools like vivid_product_sheet vs vivid_create_product_sheet are explicitly contrasted. Some overlap remains: vivid_list_references (products/testimonials) vs vivid_list_assets, and the three separate status tools (vivid_job_status, vivid_music_status, vivid_render_status) require the agent to remember which job type each one belongs to.

    Naming Consistency4/5

    Nearly everything follows a vivid_verb_noun snake_case convention with a shared prefix, which makes the set predictable. Minor deviations: noun-only names (vivid_whoami, vivid_usage) and the timeline/project vocabulary split where create/get/list_editor_project sit alongside vivid_edit_timeline and vivid_render_project.

    Tool Count3/5

    The domain is genuinely broad — multi-modal generation, asset management, product QC, a full video-editor command surface, rendering and screen recording — so 37 tools is defensible rather than bloated. Still, it sits well past the comfortable range, and several groups could be consolidated (multiple list_* and status_* tools), pushing it into heavy territory for an agent to hold in context.

    Completeness4/5

    Coverage is strong end-to-end: account/credits, upload→generate→inspect→download→share assets, product analysis and QC, testimonials, music/voice/TTS/transcription, timeline create/edit/render/status and UI recording. The notable gap is deletion — there is no tool to remove assets, references/products, editor projects or jobs, so cleanup paths dead-end even though creation and read paths are complete.

    Maintenance

    ActivityActive
    ResponsivenessSyncing