Hey n8n community
I wanted to share how you can use n8nβs built-in MCP Client Tool to connect to the Ssemble AI Clipping MCP server and automate short-form video creation from YouTube videos β no custom nodes needed.
What is Ssemble AI Clipping?
Ssemble is a video processing platform that takes YouTube videos and automatically creates TikTok/Reels/Shorts-style clips with:
AI-selected highlight moments with viral scoring
9+ caption templates (Karaoke, Bold, Minimal, etc.)
45+ background music tracks
30+ gameplay overlays (Minecraft, GTA, Subway Surfer, etc.)
159+ meme hook clips (2β5 second attention grabbers)
AI-generated titles, descriptions, and hashtags
We recently published an MCP server that exposes all of this as 9 tools any MCP client can use.
How to connect it in n8n
Since n8n has native MCP support via the MCP Client Tool node, setup is straightforward:
Step 1 β Prerequisites
Self-hosted n8n (v1.88.0+)
Set environment variable:
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
Get a Ssemble API key from: https://app.ssemble.com (Settings β API Keys)
Step 2 β Add MCP Client Tool node
Add MCP Client Tool node
Transport: SSE
URL: https://mcp.ssemble.com/mcp
Authentication: Header Auth
Header Name: X-Ssemble-API-Key
Header Value: sk_ssemble_your_key_here
Tools: All (or select specific)
Step 3 β Connect to AI Agent
Add an AI Agent node (Claude, OpenAI, etc.)
Connect MCP Client Tool as a tool input
The agent now has access to all Ssemble tools
Available tools (9 total)
Tool
Description
create_short
Submit YouTube URL for clipping (returns request ID)
get_status
Check progress (0β100%)
get_shorts
Get clips + download URLs + viral scores
list_requests
List all requests
delete_request
Delete a request
list_templates
Browse caption styles
list_music
Browse music tracks
list_game_videos
Browse gameplay overlays
list_meme_hooks
Browse meme clips
Example workflows
1. Content repurposing pipeline
RSS β detect new YouTube video β create_short β wait/poll β get_shorts β post to Slack/Discord
2. Batch processing
Google Sheet (URLs) β loop β create_short β collect request IDs β poll β save results back
3. AI-powered automation
Webhook β user input (βmake it funny with gaming overlayβ) β AI Agent chooses tools β generate clips β return results
Important: Async processing pattern
Video processing takes 5β30 minutes , so:
create_short β returns requestId instantly
get_status β check progress
get_shorts β fetch results
Tip: Add a Wait node (5β10 min) or loop with polling until completed.
Links
Would love to see what you build with this
Happy to answer any questions!
Hey friend!
Cool setup β this is a great use case for n8n.
For anyone looking for an alternative that works with both MCP and direct HTTP Request nodes , Iβve been using WayinVideo API (https://wayin.ai/api ) for the same kind of workflow.
A few things that work well for me:
AI Clipping β automatically picks the best viral moments, adds captions, reframes to 9:16 β all in one API call
Find Moments β you can describe what you want in plain English like βproduct demoβ or βfunny reactionβ and it finds those exact clips
No MCP required β works directly with n8nβs HTTP Request node, so it runs on both Cloud and self-hosted without any extra setup
Processing time is around 90 seconds for most videos β much faster than 5β30 minutes
The flow is simple:
Form Trigger / Webhook β POST video URL to WayinVideo API β Wait 90s β GET clips β each clip has download link, viral score, title, tags
Also supports YouTube, Zoom, TikTok, Vimeo, and more β just paste the URL.
Docs here if anyone wants to check it out: https://wayin.ai/api-docs/ai-clipping/
Happy to share the n8n workflow JSON too!
1 Like
Hey ssemble !
Nice guide β the webhook callback tip from Benjamin is a good catch, polling with Wait nodes does eat up execution slots fast.
Been using a similar setup for YouTube Shorts creation but without the MCP layer. The one thing that bugged me about MCP-based tools is they only work on self-hosted n8n with that environment variable set β which cuts out anyone on n8n Cloud.
What I switched to uses plain HTTP Request nodes so it runs anywhere β Cloud or self-hosted, no extra config needed. You just POST the YouTube URL, get back clips ranked by viral score with titles, timestamps, and download links. It also does 9:16 auto-reframe and animated captions in the same call, so no separate editing step.
The big difference I noticed is processing time β most videos come back in around 90 seconds instead of 5β30 minutes, which makes the polling pattern much simpler to manage.
Also has a Find Moments feature where you describe what you want in plain English β like βproduct demoβ or βaudience laughingβ β and it pulls exactly those clips. Useful when you donβt just want the top viral moments but something specific.
Docs here if anyone wants to compare: https://wayin.ai/api-docs/ai-clipping/
Happy to share the workflow JSON!
ssemble:
I wanted to share how you can use n8nβs built-in MCP Client Tool to connect to the Ssemble AI Clipping MCP server and automate short-form video creation from YouTube videos β no custom nodes needed.
What is Ssemble AI Clipping?
Ssemble is a video processing platform that takes YouTube videos and automatically creates TikTok/Reels/Shorts-style clips with:
AI-selected highlight moments with viral scoring
9+ caption templates (Karaoke, Bold, Minimal, etc.)
45+ background music tracks
30+ gameplay overlays (Minecraft, GTA, Subway Surfer, etc.)
159+ meme hook clips (2β5 second attention grabbers)
AI-generated titles, descriptions, and hashtags
We recently published an MCP server that exposes all of this as 9 tools any MCP client can use.
How to connect it in n8n
Since n8n has native MCP support via the MCP Client Tool node, setup is straightforward:
Step 1 β Prerequisites
Self-hosted n8n (v1.88.0+)
Set environment variable:
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
Get a Ssemble API key from: https://app.ssemble.com (Settings β API Keys)
Step 2 β Add MCP Client Tool node
Add MCP Client Tool node
Transport: SSE
URL: https://mcp.ssemble.com/mcp
Authentication: Header Auth
Header Name: X-Ssemble-API-Key
Header Value: sk_ssemble_your_key_here
Tools: All (or select specific)
Step 3 β Connect to AI Agent
Add an AI Agent node (Claude, OpenAI, etc.)
Connect MCP Client Tool as a tool input
The agent now has access to all Ssemble tools
Available tools (9 total)
Tool
Description
create_short
Submit YouTube URL for clipping (returns request ID)
get_status
Check progress (0β100%)
get_shorts
Get clips + Download Minecraft + viral scores
list_requests
List all requests
delete_request
Delete a request
list_templates
Browse caption styles
list_music
Browse music tracks
list_game_videos
Browse gameplay overlays
list_meme_hooks
Browse meme clips
Example workflows
1. Content repurposing pipeline
RSS β detect new YouTube video β create_short β wait/poll β get_shorts β post to Slack/Discord
2. Batch processing
Google Sheet (URLs) β loop β create_short β collect request IDs β poll β save results back
3. AI-powered automation
Webhook β user input (βmake it funny with gaming overlayβ) β AI Agent chooses tools β generate clips β return results
Important: Async processing pattern
Video processing takes 5β30 minutes , so:
create_short β returns requestId instantly
get_status β check progress
get_shorts β fetch results
Tip: Add a Wait node (5β10 min) or loop with polling until completed.
Thanks for sharing. This guide really helps me.
ssemble:
I wanted to share how you can use n8nβs built-in MCP Client Tool to connect to the Ssemble AI Clipping MCP server and automate short-form video creation from YouTube videos β no custom nodes needed.
What is Ssemble AI Clipping?
Ssemble is a video processing platform that takes YouTube videos and automatically creates TikTok/Reels/Shorts-style clips with:
AI-selected highlight moments with viral scoring
9+ caption templates (Karaoke, Bold, Minimal, etc.)
45+ background music tracks
30+ gameplay overlays (Minecraft, GTA, Subway Surfer, etc.)
159+ meme hook clips (2β5 second attention grabbers)
AI-generated titles, descriptions, and hashtags
We recently published an MCP server that exposes all of this as 9 tools any MCP client can use.
How to connect it in n8n
Since n8n has native MCP support via the MCP Client Tool node, setup is straightforward:
Step 1 β Prerequisites
Self-hosted n8n (v1.88.0+)
Set environment variable:
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
Get a Ssemble API key from: https://app.ssemble.com (Settings β API Keys)
Step 2 β Add MCP Client Tool node
Add MCP Client Tool node
Transport: SSE
URL: https://mcp.ssemble.com/mcp
Authentication: Header Auth
Header Name: X-Ssemble-API-Key
Header Value: sk_ssemble_your_key_here
Tools: All (or select specific)
Step 3 β Connect to AI Agent
Add an AI Agent node (Claude, OpenAI, etc.)
Connect MCP Client Tool as a tool input
The agent now has access to all Ssemble tools
Available tools (9 total)
Tool
Description
create_short
Submit YouTube URL for clipping (returns request ID)
get_status
Check progress (0β100%)
get_shorts
Get clips + Download Minecraft + viral scores
list_requests
List all requests
delete_request
Delete a request
list_templates
Browse caption styles
list_music
Browse music tracks
list_game_videos
Browse gameplay overlays
list_meme_hooks
Browse meme clips
Example workflows
1. Content repurposing pipeline
RSS β detect new YouTube video β create_short β wait/poll β get_shorts β post to Slack/Discord
2. Batch processing
Google Sheet (URLs) β loop β create_short β collect request IDs β poll β save results back
3. AI-powered automation
Webhook β user input (βmake it funny with gaming overlayβ) β AI Agent chooses tools β generate clips β return results
Important: Async processing pattern
Video processing takes 5β30 minutes , so:
create_short β returns requestId instantly
get_status β check progress
get_shorts β fetch results
Tip: Add a Wait node (5β10 min) or loop with polling until completed.
Can you explain how to use n8nβs built-in MCP Client Tool to connect to the Ssemble AI Clipping MCP server for automatically turning YouTube videos into short-form clips, and walk me through the setup steps, available tools, and example workflows?
the mcp client tool route is the right call here over building a custom http node.
having the model negotiate the clipping boundaries based on audio transcripts avoids so much messy manual timestamp math.
how are you handling render queues when multiple long videos arrive back-to-back? do you throttle executions in n8n or queue them upstream?