HeyGen MCP:
Video generation
for any AI agent
Connect HeyGen to Claude Web, Claude Code, Gemini CLI, Cursor, and more via the Model Context Protocol (MCP). Your agent creates, manages, and retrieves videos using your existing HeyGen plan. No extra billing.

HeyGen MCP makes video a native agent capability
AI agents are already part of your workflow. HeyGen's MCP server makes professional video creation available to any MCP-compatible agent. Not a separate step, not a separate integration.
No integration overhead
Connect to HeyGen's full video capabilities without building or maintaining any API integrations. No change logs to track.
Works where you already work
Already use Claude Web, Claude Code, Claude Desktop, Gemini CLI, or Cursor? HeyGen connects to the tools your team uses every day.
Secure by default
OAuth authentication tied to your HeyGen account. No API keys to rotate or expose. Your videos, your account, your credits.
Your avatars and voices
Any custom avatar or voice available in your HeyGen account is accessible through Remote MCP, including branded assets.
175+ languages and dialects
Agents can generate multilingual video content with AI-powered lip sync and translation, at scale and on demand in 175+ languages and dialects.
No additional billing
Video generation uses credits included in your existing HeyGen plan. Available on all plans, including free accounts.
Have questions? We have answers
Do I need an API key?
No. Remote MCP uses OAuth authentication tied to your HeyGen account (Web Plan). No API key required.
Does HeyGen’s MCP cost extra?
No. Video generation uses the premium credits included in your existing HeyGen plan. There are no separate API charges or additional billing.
Which HeyGen plans support MCP?
MCP is available on all HeyGen plans. For heavier usage, upgrading to the Creator plan or above is recommended.
Can I use my custom avatars and voices?
Yes. Any avatar or voice available in your HeyGen account, including custom-built assets, is accessible through HeyGen MCP.
What's the difference between this and the HeyGen API?
The HeyGen API gives you direct REST endpoints for programmatic control. Remote MCP wraps those capabilities so AI agents can use them conversationally without you writing integration code.

