Bring Ai Avatars
to Cline
Learn how to connect HeyGen to Cline and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the HeyGen MCP Server?
Connect your HeyGen account to any AI agent and take full control of your AI video production and avatar workflows through natural conversation.
What you can do
- Avatar Video Generation — Create high-quality videos by selecting from a diverse range of AI avatars and professional voices
- One-Shot Production — Use the AI Video Agent to generate complete videos from a single text prompt automatically
- Template Automation — Generate personalized videos at scale by replacing variables in your predefined HeyGen templates
- Asset Management — Upload media assets (images, audio, video) and manage your creation library programmatically
- Status Monitoring — Track the progress of video generation jobs and retrieve instant download links upon completion
How it works
1. Subscribe to this server
2. Retrieve your API Key from your HeyGen Dashboard (Settings > API)
3. Start generating and managing AI videos from Claude, Cursor, or any MCP client
No more manual editing or complex timeline management for simple avatar videos. Your AI acts as your dedicated video producer.
Who is this for?
- Content Marketers — scale video content production for social media and ads using automated avatar generation
- Sales Teams — create personalized video outreach at scale by automating template-based video creation
- Educational Designers — convert text lessons into engaging avatar-led videos without filming or recording
Built-in capabilities (12)
Use template for video
Create avatar video
One-shot prompt to video
Check connection
Check video status
List AI actors
List AI voices
List past creations
List design templates
Delete video
Verify credentials
Add image/audio source
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including HeyGen tool calls without waiting for prompts between steps. Connect 12 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
HeyGen in Cline
HeyGen and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HeyGen to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for HeyGen in Cline
The HeyGen MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
HeyGen for Cline
Every tool call from Cline to the HeyGen MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I choose the right avatar for my video?
Use the list_available_avatars tool to browse all options. Your agent will provide the names and unique avatar_id for each character, which you can then use in your generation requests.
Can I generate a video without specifying an avatar or voice?
Yes! Use the generate_from_prompt tool (Video Agent). Simply describe what you want, and HeyGen will automatically select the best-matching avatar and voice for your content.
Is it possible to automate personalized videos for multiple customers?
Absolutely. Use the create_from_template tool by providing a templateId and a set of variables. Your AI agent can iterate through your customer list and trigger unique videos for each person.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.