A Pro plan or higher is required on the connected workspace.
Setup
Claude (web, desktop and mobile)
- Go to Settings → Connectors → Add custom connector
- Paste
https://app.hoox.video/api/mcpand confirm - 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
/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.
Generate a full video
Generate a full video
List avatars and voices
List avatars and voices
Create a custom avatar
Create a custom avatar
Generate assets
Generate assets
Duplicate a video
Duplicate a video
Full script-to-MP4 workflow
Full script-to-MP4 workflow
Available tools
Workspace
Voices
Avatars
Folders
Script
Video generation
Export
Video management
Assets
Typical workflow
Troubleshooting
"Pro plan required" during sign-in
"Pro plan required" during sign-in
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.
Connected to the wrong workspace
Connected to the wrong workspace
The workspace is chosen once, on the authorization screen. Disconnect the Hoox connector in your client, reconnect, and pick another workspace.
Error insufficient_credits (402)
Error insufficient_credits (402)
Your workspace has run out of credits. Top up from the Hoox dashboard under Settings → Billing.
Tool not showing up in the client
Tool not showing up in the client
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.
Generation stuck in "processing"
Generation stuck in "processing"
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.
