Skip to main content
The official Model Context Protocol server for Hoox. Any MCP-compatible client can generate videos and assets, manage avatars and voices, and export MP4 files using natural language. The server is hosted by Hoox — nothing to install and no API key to manage:
When your client connects for the first time, a browser window opens on app.hoox.video: sign in, choose the workspace to connect (if you belong to several), and click Authorize. Every tool then operates on that workspace and consumes its credits. To switch workspace, disconnect and reconnect.
A Pro plan or higher is required on the connected workspace.

Setup

Claude (web, desktop and mobile)

  1. Go to Settings → Connectors → Add custom connector
  2. Paste https://app.hoox.video/api/mcp and confirm
  3. Complete the sign-in flow when prompted
On Claude Team and Enterprise plans, an admin can add the connector once from the admin settings and make it available to the whole organization. Each member still signs in with their own Hoox account the first time they use it.

Claude Code

Then run /mcp inside Claude Code to authenticate.

Cursor and other MCP clients

Add the server URL to your client’s MCP configuration:

Example prompts

Hoox credits are required to use the MCP tools.

Available tools

Workspace

Voices

Avatars

Folders

Script

Video generation

Export

Video management

Assets

Typical workflow

Troubleshooting

The MCP server can only connect workspaces on a Pro plan or higher. If none of your workspaces is eligible, upgrade at app.hoox.video.
The workspace is chosen once, on the authorization screen. Disconnect the Hoox connector in your client, reconnect, and pick another workspace.
Your workspace has run out of credits. Top up from the Hoox dashboard under Settings → Billing.
Check the connector status in your client’s settings and re-run the sign-in flow if needed. After updating the configuration, restart the client.
Video generation can take 1–5 minutes depending on duration and options. Use get_generation_status to monitor progress. If the job is stuck for more than 10 minutes, check the error field in the status response.