mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-14 18:01:20 +08:00
3f502a0c99
# Conflicts: # docs/concepts/compositions.mdx # docs/contributing.mdx # docs/docs.json # docs/guides/antigravity.mdx # docs/guides/claude-design.mdx # docs/guides/copilot-cli.mdx # docs/guides/mcp.mdx # docs/guides/open-design.mdx # docs/guides/pipeline.mdx # docs/guides/prompting.mdx # docs/guides/skills.mdx # docs/guides/video-editor-cheatsheet.mdx # docs/packages/studio.mdx # docs/quickstart.mdx
139 lines
5.6 KiB
Plaintext
139 lines
5.6 KiB
Plaintext
---
|
||
title: "Create through an AI chat"
|
||
description: "Use the hosted HyperFrames MCP connector to create and render without installing the local CLI."
|
||
---
|
||
|
||
HyperFrames MCP is a hosted connector for supported AI chat products. It lets the chat create, revise, preview, and render a HyperFrames composition through your HeyGen account.
|
||
|
||
<Note>
|
||
This path is in beta. Availability, interface wording, features, credits, and plan requirements can change.
|
||
</Note>
|
||
|
||
## Choose hosted or local
|
||
|
||
Use the hosted connector when you want:
|
||
|
||
- no local HyperFrames setup;
|
||
- a conversational creation flow;
|
||
- cloud rendering;
|
||
- previous hosted compositions available from the chat.
|
||
|
||
Use the [local Quickstart](/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:
|
||
|
||
```text
|
||
https://mcp.heygen.com/mcp/hyperframes/
|
||
```
|
||
|
||
You need a HeyGen account and access to the HyperFrames connector.
|
||
|
||
<Tabs>
|
||
<Tab title="Claude">
|
||
1. Open **Settings → Connectors**.
|
||
2. Choose **Add custom connector** and enter the MCP address above.
|
||
3. Complete the HeyGen sign-in.
|
||
4. In a new chat, open **Search and tools** and enable HyperFrames.
|
||
|
||
Claude supports remote custom connectors on Pro, Max, Team, and Enterprise plans. Team and Enterprise owners configure organization connectors before members connect. See [Anthropic’s current connector instructions](https://support.anthropic.com/en/articles/11175166-about-custom-integrations-using-remote-mcp).
|
||
</Tab>
|
||
<Tab title="ChatGPT">
|
||
If HyperFrames appears in **Settings → Apps**, choose **Connect** and complete HeyGen authorization.
|
||
|
||
To add the MCP address as a custom app with create and render actions, a supported Business or Enterprise/Edu workspace must enable developer mode. An authorized user then opens **Settings → Apps → Create**, enters the endpoint, scans the tools, completes OAuth, and creates the app. Workspace admins control publishing and action access.
|
||
|
||
See [OpenAI’s current MCP app instructions](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta).
|
||
</Tab>
|
||
<Tab title="Grok">
|
||
1. Open [grok.com/connectors](https://grok.com/connectors).
|
||
2. Choose **New Connector → Custom**.
|
||
3. Enter the MCP address above.
|
||
4. Complete HeyGen authorization.
|
||
|
||
Business and Enterprise workspaces require an administrator to provision the connector first. See [xAI’s current connector instructions](https://docs.x.ai/grok/connectors).
|
||
</Tab>
|
||
</Tabs>
|
||
|
||
Host products change their connector interfaces independently. If a menu or button is missing, check that host’s current plan and workspace permissions before treating it as a HyperFrames failure.
|
||
|
||
## Create a first composition
|
||
|
||
Describe the video as you would to an editor:
|
||
|
||
```text
|
||
Make a 15-second vertical product intro for a meditation app.
|
||
Audience: people who have trouble falling asleep.
|
||
Style: quiet, spacious, and warm.
|
||
Show the breathing timer and end with “Rest starts here.”
|
||
```
|
||
|
||
The connector can create the composition and return a preview supported by the host.
|
||
|
||
## Revise it conversationally
|
||
|
||
Continue in the same conversation:
|
||
|
||
```text
|
||
Reveal the product two seconds earlier.
|
||
Keep the current colors.
|
||
Make the captions smaller and slow down the final transition.
|
||
```
|
||
|
||
Name the visible problem and desired outcome. Avoid restarting the full brief for every revision.
|
||
|
||
## Render
|
||
|
||
Ask for the destination you need:
|
||
|
||
```text
|
||
Render this as an MP4 at 30 fps.
|
||
```
|
||
|
||
MP4 is the normal sharing format. WebM can be useful for web delivery and transparent overlays. MOV can be useful for another editing workflow.
|
||
|
||
Longer renders may continue as a background job. Ask the connector for the render status if the host does not update automatically.
|
||
|
||
## Credits and account access
|
||
|
||
Authoring and rendering can use HeyGen credits. Ask the connector to show the available balance or check your HeyGen account.
|
||
|
||
Compositions and assets are resolved through the HeyGen account or space used during authorization. If a previous composition is missing, first confirm that the connector is signed into the same account and space.
|
||
|
||
## Current limits
|
||
|
||
- Rendering runs on HeyGen infrastructure. Use the local path when you need local rendering or self-hosting.
|
||
- The connector cannot upload a new binary file from chat. Upload it to HeyGen first, then reference it by name.
|
||
- Supported aspect ratios are `16:9`, `9:16`, `1:1`, and `4:5`.
|
||
- A host with MCP widget support can show an embedded preview. Text-only clients receive a preview link.
|
||
- Precise source and pixel-level editing belongs in the local project and Studio.
|
||
|
||
## Troubleshooting
|
||
|
||
If authorization loops:
|
||
|
||
1. confirm the production MCP address;
|
||
2. disconnect and reconnect HyperFrames;
|
||
3. confirm that your host plan and workspace permit the connector;
|
||
4. confirm that pop-ups and the HeyGen sign-in window are not blocked.
|
||
|
||
If a preview or render stalls:
|
||
|
||
1. wait briefly and list the compositions or ask for the current render status;
|
||
2. retry from a new chat if the host session has expired;
|
||
3. keep the composition or job identifier if one is shown;
|
||
4. report the prompt, expected result, actual result, host, and identifier.
|
||
|
||
Use [Share feedback](/guides/feedback) when the failure belongs to HyperFrames. Use the host product’s support when the connector cannot be installed or invoked at all.
|
||
|
||
<Warning>
|
||
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.
|
||
</Warning>
|