Cliphi + Qwen
Clips from a
Qwen conversation
Qwen Code takes custom MCP servers, so Cliphi drops into its config and clipping becomes part of the conversation.
1Add Cliphi to your Qwen Code MCP config
An mcpServers entry: URL https://www.cliphi.com/api/mcp, your Cliphi key as the bearer token.
2Send your video link
Ask for clips in your own words; the job runs on Cliphi, not in the chat.
3Choose from free previews
Each moment it finds arrives as a preview link. Renders wait for your go-ahead.
Made with Cliphi
Real clips, real reach, published to YouTube Shorts, Instagram Reels, and Facebook Reels.
641Kviews
Instagram Reels
12.9Kviews
Instagram Reels
158Kviews
Instagram Reels
26Kviews
Instagram Reels
176Kviews
Instagram Reels
77Kviews
Facebook Reels
20Kviews
Facebook Reels
127Kviews
Facebook Reels
641Kviews
Instagram Reels
12.9Kviews
Instagram Reels
158Kviews
Instagram Reels
26Kviews
Instagram Reels
176Kviews
Instagram Reels
77Kviews
Facebook Reels
20Kviews
Facebook Reels
127Kviews
Facebook Reels
Qwen questions
An mcpServers entry with the Cliphi address and your key as the bearer token. It sits alongside whatever other servers you already have, and Qwen picks up the Cliphi tools the next time it starts.
No. You give Cliphi a link and it fetches the video itself, so nothing large moves through the conversation. That is why a long recording works exactly as well here as a short one.
Yes. Cliphi transcribes in the video's language, and you can state that language when you submit rather than leaving it to be detected, which gives better results on recordings that switch between two languages.
A preview link that already shows the finished treatment: the crop, the captions and the framing. You look through them and ask for the ones you want as finished clips.
Also works from
Add Cliphi to Qwen
One entry in your MCP config and clipping becomes part of the conversation.
Building your own agent or workflow? Developer docs