Skip to main content
Glama

Related Servers

Alternatives to Clips Kitty

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Open-source video pipeline (clipper, AI video & more) with a local MCP server: scout trends, download and transcribe videos, cut clips, build captioned shorts and run editing tools from your agent. Runs in the ViralMint desktop app on 127.0.0.1 with a bearer token; AGPL-3.0, bring your own API keys.
      210
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants like Claude, Cursor, and Codex to clip YouTube, Twitch, and Kick videos or live streams (downloading locally via yt-dlp), create beat-synced edits, and generate AI Studio images and video, then fetch rendered clips, captions, and post drafts. It also exposes account credits, project status, and media uploads, while never purchasing anything or publishing on the user's behalf.
      26
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes one tool per pipeline command so an AI agent can drive the work of turning audio into a reviewable vertical video draft: importing sources, transcribing with word timings, planning beats, generating one AI image per beat, and rendering a 1080×1920 MP4 with word-synced captions. Paid steps stay gated behind script approval given from the CLI, so agents can run the loop for Reels, TikTok and YouTube Shorts without overspending.
      2
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding agents to programmatically assemble vertical videos and manage local CapCut Desktop drafts, including AI background removal, audio mastering to -14 LUFS or Demucs vocal isolation, music auto-ducking, punch zooms, karaoke captions, PiP proof overlays, hook badges, safe-zone linting, proxy previews, and EN→ES cloning/dubbing. It outputs real CapCut draft JSON ready for review and export.
      17
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 19 tools

    Disambiguation2/5

    There are two near-identical plan/execute pairs (schedule_clips_plan/execute and publish_plan/publish_plan_execute) plus uploadpost_publish, and the descriptions do not make it obvious which publishing path an agent should pick. The status family is also crowded: youtube_status, woopsocial_status, uploadpost_status, publish_status, uploadpost_result, job_status, queue_status and engine_status all answer 'what state is X in', and distinguishing publish_status from uploadpost_result or job_status from queue_status requires careful reading.

    Naming Consistency3/5

    There is a recognizable <noun>_status pattern for the seven state tools, but verbs are ordered inconsistently elsewhere: schedule_clips_plan and uploadpost_publish are verb-first, while publish_plan and clip_captions are noun-first. Multi-word compounds pile up (publish_plan_execute vs schedule_clips_execute) so the naming is readable but not predictable.

    Tool Count3/5

    19 tools for a pipeline-plus-publishing server is on the heavy side, and much of the weight comes from supporting three separate publishing backends (YouTube direct, WoopSocial, Upload-Post), each with its own status/plan/execute/result tools. It is defensible for the domain but feels borderline bloated.

    Completeness3/5

    The core lifecycle is covered: ingest (queue_video, queue_local_file), monitor (job_status, queue_status), inspect (list_videos, list_clips, clip_captions), export, and multi-platform publishing with plan/execute. However, there is no cancel or delete operation for jobs, scheduled posts, or clips, and no way to revise a plan once created, which are real dead ends for an agent managing a queue.

    Maintenance

    ActivityActive
    ResponsivenessSyncing