How to Generate Faceless TikToks from Cursor with MCP (2026)

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 or REST → faceless short → webhook → export. Autopilot still owns daily TikTok/Instagram posting in the dashboard when you want cadence on rails.

Before you begin

What you’ll need:

• Cursor or another MCP client (Claude Desktop works the same pattern) — or any HTTP client for REST
• A Viibeo account and an API key (vii_… under Settings → Developers)
• 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, /llms-full.txt, and /skills/viibeo-faceless-shorts/SKILL.md. OpenAPI: /api/v1/openapi.json.

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://www.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, publish_video, and get_my_credits.

Optional: load the skill file so the agent already knows the loop and Autopilot limits — don’t make it rediscover the API every chat.

Prefer REST?

Same key, different surface:

curl "https://www.viibeo.com/api/v1/credits" \
  -H "Authorization: Bearer vii_YOUR_API_KEY"

Create a short with POST /api/v1/videos, poll GET /api/v1/jobs/{id}, export with POST /api/v1/exports. Full path table: /agents.

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:

1. Call get_my_credits if balance is unclear
2. Call create_short (or POST /api/v1/videos)
3. Wait for a generation.completed webhook — or poll get_generation_status until COMPLETED

If generation fails, fix the prompt or credit issue — don’t spam new jobs. Subscribe to generation.failed so agents don’t hang on a silent poll.

Step 3: Export the MP4

When the video exists:

1. start_export with the videoId (or POST /api/v1/exports)
2. Wait for export.ready (payload includes outputUrl) — or poll get_render_status
3. 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: Publish or hand cadence to Autopilot

One-off: publish_video / POST /api/v1/publish to connected TikTok, Instagram, or YouTube. Listen for publish.completed.

Daily cadence: In the Viibeo dashboard on Starter+, create an Autopilot series — or call create_autopilot_series from MCP/REST. Connect socials under Settings → Social first.

Webhooks (skip the busy-wait)

Under Settings → Developers, add an HTTPS endpoint and pick events. We sign every delivery:

• Header: X-Viibeo-Signature: t=<unix>,v1=<hex>
• Verify: HMAC-SHA256(secret, t + "." + rawBody)

Events: generation.completed, generation.failed, export.ready, export.failed, publish.completed. You can also manage endpoints via POST /api/v1/webhooks.

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, REST + MCP + webhooks, 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)

1. Keep create → export reliable.
2. Prefer webhooks over polling for async video jobs.
3. Point every “Agents” CTA at /agents, not a login wall.
4. Only buy amplification after organic CTR proves the story.

Related

• Agents, MCP, REST & webhooks
• How to make faceless TikTok videos with AI
• How to auto-post TikTok without showing your face
• Autopilot
• Pricing