HyperFrames MCP is a hosted connector for supported AI chat products. It lets
the chat call HyperFrames creation and rendering tools through your HeyGen
account without installing the local CLI.
This path is in beta. Availability, interface wording, features, credits, and plan requirements
can change.
Choose hosted or local
Use the hosted connector when you want:
- no local HyperFrames setup;
- a conversational creation flow;
- cloud rendering;
Use the local Quickstart when you need:
- full project files;
- local rendering;
- direct Studio and source editing;
- custom automation or deployment;
- precise debugging and validation.
Connect HyperFrames
The production MCP address is:
You need a HeyGen account and access to the HyperFrames connector.
Each host controls where custom connectors appear and which plans or workspace
roles can add them. Use the steps below as orientation, then follow the linked
host documentation when its interface differs.
- Open Customize → Connectors.
- Choose Add custom connector and enter the MCP address above.
- Complete the HeyGen sign-in.
- In a new chat, open the + menu, choose Connectors, and enable HyperFrames.
See Anthropic’s current connector instructions for plan and workspace requirements.If HyperFrames appears in Settings → Apps, choose Connect and complete HeyGen authorization.To add the MCP address as a custom app, an authorized user enables the host’s developer mode, creates an app from the endpoint, scans the tools, and completes OAuth. Workspace admins may control publishing and action access.See OpenAI’s current MCP app instructions.
- Open grok.com/connectors.
- Choose New Connector → Custom.
- Enter the MCP address above.
- Complete HeyGen authorization.
See xAI’s current connector instructions for workspace requirements.Create a first composition
Describe the video as you would to an editor:
The connector proposes and builds the composition through the tools exposed in
that chat. Follow the returned tool result rather than expecting a specific
preview widget: hosts present MCP output differently.
Revise it conversationally
Continue in the same conversation:
Name the visible problem and desired outcome. Avoid restarting the full brief for every revision.
Render
Ask for the destination you need:
MP4 is the normal sharing format. WebM can be useful for web delivery and transparent overlays. MOV can be useful for another editing workflow.
The connector renders on hosted infrastructure. Keep any composition or render
identifier the tool returns so you can refer to the same work in a follow-up.
OAuth connects the server to your current HeyGen account. Plans, limits, and
billing can change independently of HyperFrames, so confirm them in the account
before starting repeated or long renders.
Current limits
- Rendering runs on HeyGen infrastructure. Use the local path when you need local rendering or self-hosting.
- The exact tool list and result presentation depend on the deployed server and the chat host.
- Hosted output does not give you the same local project folder, Studio surface, or debugging access as the local path.
- Precise source and pixel-level editing belongs in the local project and Studio.
Troubleshooting
If authorization loops:
- confirm the production MCP address;
- disconnect and reconnect HyperFrames;
- confirm that your host plan and workspace permit the connector;
- confirm that pop-ups and the HeyGen sign-in window are not blocked.
If a create or render action stalls:
- keep the last tool result and any identifier it returned;
- retry from a new chat if the host session has expired;
- report the prompt, expected result, actual result, host, and identifier.
Use Share feedback when the failure belongs to HyperFrames. Use the host product’s support when the connector cannot be installed or invoked at all.
Only connect the production HyperFrames server shown on this page. As with any external connector,
review the permissions and do not send secrets or private material that the destination should not
receive.
