ClipMyApp

About ClipMyApp

ClipMyApp solves a narrow problem for app and SaaS makers: the product shipped, the social feed didn't. You give it a website URL — and optionally a screen recording of the app — and it produces short-form posts for TikTok, Instagram Reels and YouTube Shorts, then schedules them to connected accounts. Three post formats come out of the same source material: creator-style UGC video with a real person on camera over real app footage, memes built from a template plus generated background and product copy, and multi-slide carousels telling a product story. The website alone is enough to start; a recording is what buys you posts that actually show the app in motion. Two things separate it from the generic AI-video crowd. First, approval is structural rather than optional — drafts land in a review queue and nothing publishes until you keep it, and the credit model reflects that: credits are spent only on posts you keep, and a failed generation refunds automatically. Second, the whole product is exposed over a hosted MCP server at api.clipmyapp.com/mcp, so Claude or any MCP-capable assistant can list recordings, generate drafts, request specific edits ('make the second hook shorter, swap the background music'), approve or reject, and schedule — 23 tools across understand / create / review / publish. That surface is OAuth-scoped into four permissions (content:read, content:generate, content:decide, publish:schedule), which means an assistant can be given drafting rights without being given the ability to post to a live account. A REST API covers the same ground for non-MCP clients. The honest limitation is scope: this is built for one thing, promoting a software product on three vertical-video platforms, and the plan tiers are sized in videos per month rather than seats.

Key Features

Tags