ClipLaunch

io.cliplaunchPublished by cliplaunch.ioOfficial publisherv1.0.1Updated Nov 1, 2026

Promo videos for Reels, YouTube and Meta ads from your URL and real screenshots, music on the beat.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

ClipLaunch is a remote MCP server that lets an assistant generate promo videos for Reels, YouTube and Meta ads from a URL and real screenshots, with music…

What you can do
  • Turn a URL and real screenshots into promo videos for Reels, YouTube and Meta ads.
  • Produce short-form marketing video output with music timed to the beat.
  • No tool list is published, so the exact operations the assistant can call are not documented here.
When to use it
Consider it when you want marketing or social promo videos generated from a product or landing page URL without editing footage by hand, and you are comfortable connecting an OAuth-authorized third-party video service.
Requirements
A remote endpoint at cliplaunch.io over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. Network access is needed.
Before you install
OAuth grants the service access to your account, and the URL and screenshots you supply are sent to a third party. Video generation may consume paid credits or quota; check pricing and what the OAuth scopes allow before connecting.

Installation

In SourceWeft

  1. Open ClipLaunch in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.cliplaunch%2Fcliplaunch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cliplaunch": {
      "type": "http",
      "url": "https://cliplaunch.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 1, 2026
  2. v1.0.0Oct 31, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.