HyperFrames by HeyGen

Yes. HeyGen's CLI reference states plainly that on hosted cloud rendering you pay per credit, and credits are HeyGen's single billing currency across every feature. Paid plans start at 1,000 credits a month for 49 US dollars. Rendering runs on HeyGen infrastructure through your connected account, so each render an agent triggers draws down that allowance.

Anthropic's directory lists two, compose and render_video, and that is the only enumeration anywhere. HeyGen publishes no tool list. Its own MCP guide states that the exact tool list depends on the deployed server and the chat host, so treat two as a snapshot of one deployment rather than a fixed total.

The renderer is; the hosted connector is not. HeyGen publishes HyperFrames under Apache 2.0 with roughly 42,000 stars, but that repository contains only the MCP documentation page — no server implementation. The endpoint at mcp.heygen.com is closed-source hosted infrastructure, so the open-source licence gives you no ability to audit what the connector actually does.

Only identity claims, which grant no boundary at all. Both the RFC 9728 resource descriptor and HeyGen's authorization server advertised exactly openid, profile and email on 2026-08-22. No scope mentions rendering, spending or composing, so consent cannot separate drafting a composition from triggering a billed render.

No tool in the listing carries a delete verb, but HeyGen's own CLI has a cloud delete command that soft-deletes a render, after which fetches return 404 and the signed video URL stops working. Whether the hosted connector exposes that path is unknown, because HeyGen publishes no tool list and no OAuth scope names deletion either way.

It may bill you twice. HeyGen documents that its upload endpoint is not idempotent on its own and that a retry without an idempotency key would create a duplicate asset and bill the workspace twice. The CLI exposes an idempotency-key flag to prevent this; whether the MCP connector sets one is not documented.

HeyGen documents connection steps for Claude, ChatGPT and Grok, each as a custom connector pointed at the production MCP address. All three require a HeyGen account plus access to the HyperFrames connector, and HeyGen notes that each host controls which plans and workspace roles may add custom connectors at all.

HeyGen's troubleshooting steps are to confirm the production MCP address, disconnect and reconnect HyperFrames, verify that your host plan and workspace permit the connector, and confirm that pop-ups and the HeyGen sign-in window are not blocked. HeyGen also warns to connect only the production server shown in its own documentation.