How to Generate Faceless TikToks from Cursor with MCP (2026)
Stop switching tabs for every short. Connect Viibeo’s MCP in Cursor, create a faceless TikTok from chat, export the MP4, and hand cadence off to Autopilot.
Most faceless creators still bounce between a chat window, a video tool, CapCut, and TikTok Studio. Agents collapsed the first half of that stack: if your IDE can call tools, the bottleneck is no longer “write a script” — it’s whether the video product is agent-ready.
This is the workflow we built for Viibeo: Cursor (or Claude) → MCP → faceless short → export. Autopilot still owns daily TikTok/Instagram posting in the dashboard. Agents create; the series posts.
Key takeaways
- Agent-native surfaces win the interest graph: a public skill + MCP docs beat a login-gated API page.
- The loop is four tools:
create_short→ poll status →start_export→ poll render. - Niche-specific prompts beat “make something viral.”
- Autopilot (Starter+) posts to TikTok and Instagram; agents list series today, they don’t create them yet.
- Free exports can be watermarked — say that before you celebrate the first MP4.
Before you begin
What you’ll need:
- Cursor or another MCP client (Claude Desktop works the same pattern)
- A Viibeo account and an API key (
vii_…under Settings → API Keys) - Credits on the account
- Time: ~10 minutes to connect; first short usually finishes in a few minutes once generation starts
- Difficulty: Intermediate (comfortable pasting JSON config)
Public docs and the installable skill live at /agents and /skills/viibeo-faceless-shorts/SKILL.md.
Step 1: Add Viibeo as an MCP server
In Cursor MCP settings (or your client’s config), point at the HTTP endpoint:
{
"mcpServers": {
"viibeo": {
"url": "https://viibeo.com/api/mcp",
"headers": {
"Authorization": "Bearer vii_YOUR_API_KEY"
}
}
}
}
Reload the client. You should see tools like create_short, get_generation_status, start_export, and get_my_credits.
Optional: load the skill file so the agent already knows the poll loop and Autopilot limits — don’t make it rediscover the API every chat.
Step 2: Ask for one concrete short
Bad: “Make a viral TikTok.”
Better: “Create a 30-second faceless true-crime short: three documented facts about the 1890s poison ring, documentary tone, strong hook in the first line.”
Then let the agent:
- Call
get_my_creditsif balance is unclear - Call
create_short - Poll
get_generation_statuswith thejobIduntilCOMPLETED
If generation fails, fix the prompt or credit issue — don’t spam new jobs.
Step 3: Export the MP4
When the video exists:
start_exportwith thevideoId- Poll
get_render_statusuntil the download URL is ready - Download and review audio + captions before you post
On Free, expect a watermark. Lite+ removes it. That distinction matters when you share “agent-made” clips publicly.
Step 4: Hand cadence to Autopilot (humans still win here)
Agents are great at one-off creation. Daily posting still needs a series: niche theme, cadence, connected TikTok and/or Instagram.
In the Viibeo dashboard on Starter+, create an Autopilot series and connect socials. From MCP, list_autopilot_series is read-only today — creating series in chat is on the roadmap, not the current contract.
YouTube Shorts remain export-then-upload.
Why this matters (the strategy, not the buttons)
Social scheduling tools that only ship a human UI lose when someone tweets “just ask your agent.” The winners make the agent path as obvious as the homepage CTA: public skill, public docs, same credits, no support ticket to start.
If you build for creators and for agents, every viral MCP/Cursor thread becomes a warm install — not a bounce to a marketing page that can’t authenticate.
What to ship next (for operators copying this)
- Keep MCP reliable (create → export must not flake).
- Publish one long-form narrative (this post / an X article) with a real config snippet.
- Point every “Agents” CTA at /agents, not a login wall.
- Only buy amplification after organic CTR proves the story.